Description Dusko 2005-11-09 16:01:42 EST

The actual culprits are ResourceUtil.load(...) and 
MSLEditingDomain.loadResource(...) methods. They attempt to load resource and 
if the load method throws an exception, they unload it. On the other hand, the 
algorithm that determined if the resource is loaded has changed from checking 
if a root object has been added to checking a flag, changing the timing.

Methods ResourceUtil.load(...) and MSLEditingDomain.loadResource(...) are 
atomic operations: when they return the resource is not loaded so there should 
not be notification that it is loaded (even though it is followed by the 
unload notification).

This is marked as critical because of the following:
1) This is regression that puts existing code in a bad shape.
2) Most event listeners handling those events are running in either asyncExec, 
syncExec or UIJob. Depending on which methods they chose they run in different 
troubles, ranging from wasted processing and memory to bad things in the UI 
(like multiple dialog boxes in one case).