As of today, I get this assertion almost every time I exit: Assertion: "uh oh, couldn't Init() for some reason" (NS_SUCCEEDED(rv)) at file nsWindowMediator.cpp, line 359 If I look at nsWindowMediator.cpp around that line, I also see the scary comment: // This should really be done in the static constructor fn. I hope this is figurative and this really isn't using a static constructor, since those don't work on lots of platforms and have caused lots of problems in the past.
Add davidm to cc list; david, any clues?
reassign to davidm. david: i think what may be going on here is that somebody is trying to get the window mediator service during XPCOM shutdown. We should probably just make this fail gracefully.
I would ignore the comment since I I think it was just copy and pasted from the bookmarks code. There are static variables but as far as I know know static constructors being used. I would step through the Init routine in the constructor ( why this is being called when you exit I don't know. Some of the exiting code we have is just broken but that is a different bug) and and see which of the cases is actually failing. In response to waterson's message, I guess it could be changed to a warning rather than assertion although I am still think something is broken in that this is being called during xpcom shut down. I am guessing it's the hidden window but that is just a guess.
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
The real problem was somebody added in some hidden window crap, and after they fixed the crash due to the window not being in the appshell window list they didn't move the window mediator code to after the test they added. fix checked in
Looks ok with today build. Marking Verified.
You need to log in before you can comment on or make changes to this bug.