I don't know exactly what I did to cause this. I can't always reproduce this. When I do reproduce it, it seems to have to do with block transformations and where the selection is after an operation. I do know that the superficial cause is that theRangeList's count never changes because theRange->SetEnd returns an error. This error is ignored in the code, and since we make no progress through the array, we're stuck. This code should be checking error results and break out of the loop on error.

making the range gravity code complain louder (and not lock up) when things are horked will happen real soon now (like today). But something somewhere is very wrong if we are getting errors here. i suspect a deeper bug... Steve, give me a heads up if you can drive this bug with a test case. I've never seen it happen.

ranges should not infinite loop anymore - tough for me to verify since i never saw the bug, but i maded the needed code mods.

Fixed in June 2 Build.