The platform behavior is really complicated, and often fixing one problem will cause changes in other situations. It looks like that happened again. I made a slight tweak to the algorithm for the next build - hopefully that will fix this case without regressing the original one again...