Closed Bug 106307 Opened 23 years ago Closed 23 years ago

M095 Trunk Crash starting mail [@ nsHashtable::Get]

Categories

(MailNews Core :: Backend, defect, P1)

x86
Windows 2000
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME
mozilla0.9.6

People

(Reporter: greer, Assigned: Bienvenu)

Details

(Keywords: crash, topcrash)

Crash Data

Talkback shows 31 incidents of users crashing at nsHashtable::Get. Most are
crashing Mail/News at launch of the mail client. (primarily on Win2000, a few
incidents on 95 and 98) 

M095 comments:
     (37044511) Comments: Attempting to open the messenger window (from the
lower -left of the browser window)
     (37024147) Comments: Trying to open messenger from the component toolbar
     (37002612) Comments: Defined first Email account(IMAP server & outgoing
SMTP different)
     (37000069) Comments: Sending mail. Mail had been composed and the Send
button depressed.
     (36914732) Comments: tried to start up email application - mozilla email
     (36884763) Comments: open mail&news windows
     (36860427) Comments: Launching mail (for the first time after updating to a
new version).
     (36814091) URL: http://www.lwn.net/daily/
     (36814091) Comments: Clicked on mail icon (bottom left)
     (36727271) Comments: Starting newsreader
     (36694822) Comments: In Browser and clicked on mail/news icon in lower left
of browser.Crashed.
     (36672520) Comments: opening mail and news
     (36648925) Comments: Starting mail client with bottom icons.
Trunk Comments:
     (36895796) Comments: crash opening mail.
     (36699500) Comments: When I choose "mail & newsgrops" from task menu

Stack Trace:
         nsHashtable::Get      
[d:\builds\seamonkey\mozilla\xpcom\ds\nsHashtable.cpp  line 313]
         nsSupportsHashtable::Get      
[d:\builds\seamonkey\mozilla\xpcom\ds\nsHashtable.cpp  line
897]
         nsMsgFolderCache::GetCacheElement
[d:\builds\seamonkey\mozilla\mailnews\base\src\nsMsgFolderCache.cpp  line 368]
         nsMsgDBFolder::GetFolderCacheElemFromFileSpec
[d:\builds\seamonkey\mozilla\mailnews\base\util\nsMsgDBFolder.cpp  line 383]
         nsMsgDBFolder::ReadDBFolderInfo
[d:\builds\seamonkey\mozilla\mailnews\base\util\nsMsgDBFolder.cpp  line 408]
         nsMsgDBFolder::GetFlags
[d:\builds\seamonkey\mozilla\mailnews\base\util\nsMsgDBFolder.cpp  line 918]
         nsMsgLocalMailFolder::AddSubfolder
[d:\builds\seamonkey\mozilla\mailnews\local\src\nsLocalMailFolder.cpp  line 290]
         nsMsgLocalMailFolder::CreateSubFolders
[d:\builds\seamonkey\mozilla\mailnews\local\src\nsLocalMailFolder.cpp  line 251]
         nsMsgLocalMailFolder::GetSubFolders
[d:\builds\seamonkey\mozilla\mailnews\local\src\nsLocalMailFolder.cpp  line 481]
         nsMsgFolderDataSource::createFolderChildNode
[d:\builds\seamonkey\mozilla\mailnews\base\src\nsMsgFolderDataSource.cpp  line 1762]
         nsMsgFolderDataSource::createFolderNode
[d:\builds\seamonkey\mozilla\mailnews\base\src\nsMsgFolderDataSource.cpp  line 1029]
         nsMsgFolderDataSource::GetTarget
[d:\builds\seamonkey\mozilla\mailnews\base\src\nsMsgFolderDataSource.cpp  line 374]
         CompositeDataSourceImpl::GetTarget
[d:\builds\seamonkey\mozilla\rdf\base\src\nsCompositeDataSource.cpp  line 830]
         nsRDFConInstanceTestNode::FilterInstantiations
[d:\builds\seamonkey\mozilla\content\xul\templates\src\nsRDFConInstanceTestNode.cpp
 line 177]
         TestNode::Propogate
[d:\builds\seamonkey\mozilla\content\xul\templates\src\nsRuleNetwork.cpp  line 1045]
         TestNode::Propogate
[d:\builds\seamonkey\mozilla\content\xul\templates\src\nsRuleNetwork.cpp  line 1060]
         TestNode::Propogate
[d:\builds\seamonkey\mozilla\content\xul\templates\src\nsRuleNetwork.cpp  line 1060]
         TestNode::Propogate
[d:\builds\seamonkey\mozilla\content\xul\templates\src\nsRuleNetwork.cpp  line 1060]
         RootNode::Propogate
[d:\builds\seamonkey\mozilla\content\xul\templates\src\nsRuleNetwork.cpp  line 765]
         nsXULContentBuilder::CreateContainerContents
[d:\builds\seamonkey\mozilla\content\xul\templates\src\nsXULContentBuilder.cpp 
line 1281]
         nsXULContentBuilder::CreateTemplateAndContainerContents
[d:\builds\seamonkey\mozilla\content\xul\templates\src\nsXULContentBuilder.cpp 
line 1206]
         nsXULContentBuilder::Rebuild
[d:\builds\seamonkey\mozilla\content\xul\templates\src\nsXULContentBuilder.cpp 
line 1728]
         nsXULContentBuilder::Rebuild
[d:\builds\seamonkey\mozilla\content\xul\templates\src\nsXULContentBuilder.cpp 
line 1745]
         nsXULTemplateBuilder::AttributeChanged
[d:\builds\seamonkey\mozilla\content\xul\templates\src\nsXULTemplateBuilder.cpp
 line 347]
         nsXULContentBuilder::AttributeChanged
[d:\builds\seamonkey\mozilla\content\xul\templates\src\nsXULContentBuilder.cpp 
line 1809]
         nsXULDocument::AttributeChanged
[d:\builds\seamonkey\mozilla\content\xul\document\src\nsXULDocument.cpp  line 1768]
         nsXULElement::SetAttr
[d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp  line 3102]
         nsXULElement::SetAttribute
[d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp  line 1434]
         XPTC_InvokeByIndex
[d:\builds\seamonkey\mozilla\xpcom\reflect\xptcall\src\md\win32\xptcinvoke.cpp 
line 154]
         XPCWrappedNative::CallMethod
[d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednative.cpp  line 1953]
         XPC_WN_CallMethod
[d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp 
line 1255]
         js_Invoke      [d:\builds\seamonkey\mozilla\js\src\jsinterp.c  line 811]
         js_Interpret   [d:\builds\seamonkey\mozilla\js\src\jsinterp.c  line 2733]
         js_Invoke      [d:\builds\seamonkey\mozilla\js\src\jsinterp.c  line 827]
         js_InternalInvoke      [d:\builds\seamonkey\mozilla\js\src\jsinterp.c 
line 902]
         JS_CallFunctionValue   [d:\builds\seamonkey\mozilla\js\src\jsapi.c 
line 3389]
         nsJSContext::CallEventHandler
[d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp  line 980]
         nsJSEventListener::HandleEvent
[d:\builds\seamonkey\mozilla\dom\src\events\nsJSEventListener.cpp  line 156]
         nsEventListenerManager::HandleEventSubType
[d:\builds\seamonkey\mozilla\content\events\src\nsEventListenerManager.cpp  line
1214]
         nsEventListenerManager::HandleEvent
[d:\builds\seamonkey\mozilla\content\events\src\nsEventListenerManager.cpp  line
1889]
         GlobalWindowImpl::HandleDOMEvent
[d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp  line 624]
         DocumentViewerImpl::LoadComplete
[d:\builds\seamonkey\mozilla\content\base\src\nsDocumentViewer.cpp  line 1110]
         nsDocShell::EndPageLoad       
[d:\builds\seamonkey\mozilla\docshell\base\nsDocShell.cpp
line 3747]
         nsWebShell::EndPageLoad       
[d:\builds\seamonkey\mozilla\docshell\base\nsWebShell.cpp
line 918]
         nsDocShell::OnStateChange     
[d:\builds\seamonkey\mozilla\docshell\base\nsDocShell.cpp
line 3668]
         nsDocLoaderImpl::FireOnStateChange
[d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp  line 1110]
         nsDocLoaderImpl::doStopDocumentLoad
[d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp  line 749]
         nsDocLoaderImpl::DocLoaderIsEmpty
[d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp  line 647]
         nsDocLoaderImpl::DocLoaderIsEmpty
[d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp  line 650]
         nsDocLoaderImpl::OnStopRequest
[d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp
line 578]
         nsLoadGroup::RemoveRequest
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsLoadGroup.cpp  line 537]
         imgRequestProxy::OnStopRequest
[d:\builds\seamonkey\mozilla\modules\libpr0n\src\imgRequestProxy.cpp  line 385]
         imgRequest::OnStopRequest
[d:\builds\seamonkey\mozilla\modules\libpr0n\src\imgRequest.cpp  line 681]
         ProxyListener::OnStopRequest
[d:\builds\seamonkey\mozilla\modules\libpr0n\src\imgLoader.cpp  line 430]
         nsJARChannel::OnStopRequest
[d:\builds\seamonkey\mozilla\netwerk\protocol\jar\src\nsJARChannel.cpp  line 614]
         nsOnStopRequestEvent::HandleEvent
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsRequestObserverProxy.cpp  line 177]
         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]
         nsAppShellService::Run
[d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsAppShellService.cpp  line 457]
         main1  [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp 
line 1305]
         main   [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp 
line 1622]
         WinMain       
[d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp  line 1640]
         WinMainCRTStartup()
Keywords: crash, topcrash
not a mail database issue. Also, a strange stack. I haven't seen this - I wonder
if it's been fixed. What are the dates of the builds showing the crash? Adding
Seth and Pav to the cc list in case it rings any bells.
Component: Mail Database → Mail Back End
The crash has shown up in the M095 release and these Trunk builds:
2001101912 (2)
2001101806
2001101606
2001101411
I was hit by this crash a couple of times last week.  It hasn't happened
recently but putting in 0.9.6 based on the fact that it was still happening on
the 10/19 build and we currently don't know if it was fixed.
Keywords: nsbeta1+
Priority: -- → P1
Target Milestone: --- → mozilla0.9.6
this has not shown up in any build after 10/19. I'll keep looking at talkback
but I suspect this is fixed.
Most of the crashes were from the 0.9.5 branch and the trunk ones have stopped
coming in.  I was hit by this a couple of times and haven't seen it in almost
two weeks worth of trunk builds, so I'm not against marking this WFM.
resolving wfm.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
marking verified worksforme based on scott's and david's last comments.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
Crash Signature: [@ nsHashtable::Get]
You need to log in before you can comment on or make changes to this bug.