Early M091 topcrash report Stack Trace: nsMsgStatusFeedback::OnStateChange [d:\builds\seamonkey\mozilla\mailnews\base\src\nsMsgStatusFeedback.cpp line 131] nsDocLoaderImpl::FireOnStateChange [d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp line 1096] nsDocLoaderImpl::doStopDocumentLoad [d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp line 736] nsDocLoaderImpl::DocLoaderIsEmpty [d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp line 633] nsDocLoaderImpl::OnStopRequest [d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp line 564] nsLoadGroup::RemoveRequest [d:\builds\seamonkey\mozilla\netwerk\base\src\nsLoadGroup.cpp line 517] imgRequestProxy::OnStopRequest [d:\builds\seamonkey\mozilla\modules\libpr0n\src\imgRequestProxy.cpp line 381] imgRequest::OnStopRequest [d:\builds\seamonkey\mozilla\modules\libpr0n\src\imgRequest.cpp line 639] ProxyListener::OnStopRequest [d:\builds\seamonkey\mozilla\modules\libpr0n\src\imgLoader.cpp line 373] nsStreamListenerTee::OnStopRequest [d:\builds\seamonkey\mozilla\netwerk\base\src\nsStreamListenerTee.cpp line 25] nsHttpChannel::OnStopRequest [d:\builds\seamonkey\mozilla\netwerk\protocol\http\src\nsHttpChannel.cpp line 2068] nsOnStopRequestEvent::HandleEvent [d:\builds\seamonkey\mozilla\netwerk\base\src\nsRequestObserverProxy.cpp line 159] PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c line 591] PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c line 524] _md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c line 1072] KERNEL32.DLL + 0x24407 (0xbff94407) 0x00688b5e Source File : http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/mailnews/base/src/nsMsgStatu sFeedback.cpp line : 131 (31565628) Comments: Clicked on the messenger icon in the browser window. Note many text aren't displayed in the GUI (menu items (31554279) Comments: I was trying to start the message center (31529427) Comments: Loading the e-mail part of mozillaI had just applied the modern theme and could not see any options for mail+news preferences in the preferences window. The controls were (radio buttons etc..) there but the text was missing. (31517482) Comments: I tried opening the mail-client by clicking on the icon two times (31513972) Comments: Started Mozilla as Administrator on Win2000 wit 'run as....'some entries of the menues did not appear....clickung around resulted in the access violation (31510635) Comments: Tried to Configure E-Mail. E-Mail is already configured in Netscape 6.01 and I use a different Profile with Mozilla (31483197) Comments: Opened Mozilla Mail and News for the second time (31483126) Comments: I opened Mozilla Mail and News for the very first time (31477520) Comments: Started up mail client (31468819) Comments: Visited the Mozilla 0.9.1 milestone release site

I believe I am experiencing the same bug on the MacIntosh. I am using the Nightly Mozilla build from June 13 (using the Modern Theme) on a G3 Mac with OS 8.6. Here is what happens: 1. Launch Mozilla 2. Use the Mac menu bar to select mail under tasks and select Mail. 3. Mozilla crashes before another screen appears. I believe the paltform should be changed to include the MacIntosh. (Sorry if this isn't the same bug.)

The stack trace is very similar to bug 84353 which is now fixed with bug 81576. Close as dupe?

Putting in 0.9.2 This is showing up in some trunk builds as well. One of the linux comments from 0.9.1 has: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: XStringBundle.stringBundle (getter) :: onget :: line 5" data: no] Failed to get stringbundle: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE)

PDT+

Please update the status whiteboard with an eta.

varada and I working on a fix...

I think the problem is mBundle is a static nsCOMPtr. there's a bug (or document) about why not to use static nsCOMPtrs, I'll go look for it.

r=varada

+ NS_ENSURE_TRUE(mBundle, NS_ERROR_NULL_POINTER); should be NS_ENSURE_ARG_POINTER(mBundle); (which automatically returns ns_error_null_pointer if mBundle would be null) after that, r=hwaara too.

I only use NS_ENSURE_ARG_POINTER(foo) if foo was an ARG.

sr=alecf

a=chofmann

fixed.

it's bad if we occasionally fail to get the string bundle. that kind of sounds familiar, I remember ben tweaking the profile manager javascript to handle the case where we'd fail to get the string bundle. ben, do you remember that bug? do you remember what the problem was? I couldn't find any other bugs about string bundles failing, perhaps this rings a bell for tao or valeski.

Using build 2001-06-28 on win, mac and linux, I don't crash starting up mail. I read through the talkback comments and didn't see anything special scenario to cause this crash. I also tested the scenario in the comment on 2001-06-13. Verfied, if this comes back or is still showing up in talkback reports reopen and give steps to reproduce.

I've got a reproducable case where we assert (before, we would have crashed.) see bug #88876

The number one cause of failing stringbundle is an unsuccessful chrome URL conversion - wrong provider type/name or wrong packaging destination. Seth might be referring to the bundle failure introduced by the obsolete stringbundle fallback mechanism. It'd be interesting to see if there are other misusage of the static nsCOMPtrs.