Closed Bug 551430 Opened 15 years ago Closed 12 years ago

crash [@ nsImapMailFolder::GetDBFolderInfoAndDB(nsIDBFolderInfo**, nsIMsgDatabase**)]

Categories

(MailNews Core :: Database, defect)

x86
All
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: wsmwk, Unassigned)

Details

(Keywords: crash, regression)

Crash Data

crash [@ nsImapMailFolder::GetDBFolderInfoAndDB(nsIDBFolderInfo**, nsIMsgDatabase**)] #109 crash for v3.0.3. no v3.1 or trunk crashes xref bug 460416 which was also nsImapMailFolder::GetDBFolderInfoAndDB bp-586f6faf-b6f8-4637-a142-0c4492100310 v3.0.3 0 thunderbird.exe nsImapMailFolder::GetDBFolderInfoAndDB mailnews/imap/src/nsImapMailFolder.cpp:2108 1 thunderbird.exe nsImapProtocol::SetupWithUrl mailnews/imap/src/nsImapProtocol.cpp:730 2 thunderbird.exe nsImapProtocol::LoadImapUrl mailnews/imap/src/nsImapProtocol.cpp:1979 3 thunderbird.exe nsImapIncomingServer::GetImapConnectionAndLoadUrl mailnews/imap/src/nsImapIncomingServer.cpp:439 4 thunderbird.exe nsImapService::GetImapConnectionAndLoadUrl mailnews/imap/src/nsImapService.cpp:2190 5 thunderbird.exe nsImapService::FolderCommand mailnews/imap/src/nsImapService.cpp:1474 6 thunderbird.exe nsImapService::UpdateFolderStatus mailnews/imap/src/nsImapService.cpp:1525 7 thunderbird.exe nsImapMailFolder::UpdateStatus mailnews/imap/src/nsImapMailFolder.cpp:1431 8 thunderbird.exe nsImapMailFolder::InitiateAutoSync mailnews/imap/src/nsImapMailFolder.cpp:9060 9 thunderbird.exe nsAutoSyncManager::TimerCallback mailnews/imap/src/nsAutoSyncManager.cpp:351 10 xpcom_core.dll nsTimerImpl::Fire xpcom/threads/nsTimerImpl.cpp:420 same person, but on v3.0.1, with comment "I update from the latest 2 version to the current 3 version. The system is much slower and crashes (never crashed V2 before)" - so marking regression bp-517166dd-d2b9-453e-8da9-870442100222 0 thunderbird.exe nsImapMailFolder::GetDBFolderInfoAndDB mailnews/imap/src/nsImapMailFolder.cpp:2108 1 thunderbird.exe nsMsgDBFolder::OnFlagChange mailnews/base/util/nsMsgDBFolder.cpp:4228 2 thunderbird.exe nsMsgDBFolder::ClearFlag mailnews/base/util/nsMsgDBFolder.cpp:4203 3 thunderbird.exe nsImapIncomingServer::DiscoveryDone mailnews/imap/src/nsImapIncomingServer.cpp:1615
#95 for v3.1.7. no correlations. EXCEPTION_ACCESS_VIOLATION_READ 0x0 bp-468e253c-7f70-43d9-bac0-b51412110121 0 thunderbird.exe nsImapMailFolder::GetDBFolderInfoAndDB mailnews/imap/src/nsImapMailFolder.cpp:2141 1 thunderbird.exe nsMsgDBFolder::ChangeNumPendingUnread mailnews/base/util/nsMsgDBFolder.cpp:4098 2 thunderbird.exe nsImapMailFolder::UpdateImapMailboxInfo mailnews/imap/src/nsImapMailFolder.cpp:2899 3 xpcom_core.dll NS_InvokeByIndex_P xpcom/reflect/xptcall/src/md/win32/xptcinvoke.cpp:102 4 xpcom_core.dll nsProxyObjectCallInfo::Run xpcom/proxy/src/nsProxyEvent.cpp:181 5 xpcom_core.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:527 6 xpcom_core.dll NS_ProcessNextEvent_P objdir-tb/mozilla/xpcom/build/nsThreadUtils.cpp:250 7 thunderbird.exe nsBaseAppShell::Run widget/src/xpwidgets/nsBaseAppShell.cpp:177 8 thunderbird.exe nsAppStartup::Run toolkit/components/startup/src/nsAppStartup.cpp:183 9 thunderbird.exe XRE_main toolkit/xre/nsAppRunner.cpp:3483 10 thunderbird.exe NS_internal_main mail/app/nsMailApp.cpp:101 11 thunderbird.exe wmain toolkit/xre/nsWindowsWMain.cpp:120 12 thunderbird.exe __tmainCRTStartup objdir-tb/mozilla/memory/jemalloc/crtsrc/crtexe.c:591 unfortunately, no reporters = no testcase
Version: unspecified → Trunk
Crash Signature: [@ nsImapMailFolder::GetDBFolderInfoAndDB(nsIDBFolderInfo**, nsIMsgDatabase**)]
no useful crash comments in last few months. v7 example bp-9545ac61-564e-4d3b-82e4-68a802111006
OS: Windows Vista → All
common crashes appear to have ended with version 9 such as bp-e61b121a-8103-4163-914b-8529e2121102 9.0.1 bugzilla@1677 2107 nsresult rv = GetDatabase(); hg@0 2108 if (NS_FAILED(rv)) hg@0 2109 return rv; hg@0 2110 hg@0 2111 NS_ADDREF(*db = mDatabase); a related patch must landed in version 10 but I'm not finding it.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.