nsObjectLoadingContent::ObjectURIChanged should revoke the events that are posted with it as owner. this is necessary so that previous async events don't interfere with potential sync instantiates done by this function.

OK, found a way to do this that avoids calling RevokeEvents in the common case (I fear that it's expensive, what with entering the monitor and iterating over all events in the queue) We only need to revoke any events if our current type is eType_Plugin: Only in those cases can we have a posted event. Fallback/UnloadContent does not need to call it. either we have no frame, or we kill the frame. so the frame comparison in HandleEvent would fail. I wonder if HandleEvent should compare mURI/mContentType against the current uri/type, though...

Checking in content/base/src/nsObjectLoadingContent.cpp; /cvsroot/mozilla/content/base/src/nsObjectLoadingContent.cpp,v <-- nsObjectLoadingContent.cpp new revision: 1.12; previous revision: 1.11 done