Closed
Bug 1581075
Opened 5 years ago
Closed 3 years ago
Crash in [@ nsCOMPtr_base::assign_from_qi_with_error | NS_GetWeakReference] via nsMsgMailNewsUrl::SetMsgWindow and nsImapService::FetchMimePart
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: wsmwk, Unassigned)
References
Details
(Keywords: crash)
Crash Data
Not new to version 68, but crash rate Signature appears to have increased
bp-d2d5cb3f-1619-4d19-a2e3-74c320190912.
Top 10 frames of crashing thread:
0 xul.dll nsCOMPtr_base::assign_from_qi_with_error xpcom/base/nsCOMPtr.cpp:55
1 xul.dll NS_GetWeakReference xpcom/base/nsWeakReference.cpp:91
2 xul.dll nsMsgMailNewsUrl::SetMsgWindow comm/mailnews/base/util/nsMsgMailNewsUrl.cpp:318
3 xul.dll nsImapService::FetchMimePart comm/mailnews/imap/src/nsImapService.cpp:369
4 xul.dll nsMessenger::SaveAttachment comm/mailnews/base/src/nsMessenger.cpp:671
5 xul.dll nsSaveMsgListener::OnStopRequest comm/mailnews/base/src/nsMessenger.cpp:1724
6 xul.dll nsStreamConverter::OnStopRequest comm/mailnews/mime/src/nsStreamConverter.cpp:945
7 xul.dll nsresult `anonymous namespace'::SyncRunnable2<nsIImapMailFolderSink, const char*, nsIImapUrl*>::Run comm/mailnews/imap/src/nsSyncRunnableHelpers.cpp:121
8 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1175
9 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:486
Reporter | ||
Comment 1•5 years ago
|
||
Does this also require the analysis of bug 1586494 comment 10?
Flags: needinfo?(benc)
Summary: Crash in [@ nsCOMPtr_base::assign_from_qi_with_error | NS_GetWeakReference] via nsMsgMailNewsUrl::SetMsgWindow → Crash in [@ nsCOMPtr_base::assign_from_qi_with_error | NS_GetWeakReference] via nsMsgMailNewsUrl::SetMsgWindow and nsImapService::FetchMimePart
Reporter | ||
Comment 2•3 years ago
|
||
v68 crashes all through 68.12.1, but virtually no version 78 crashes. Hard to determine when it was fixed, or perhaps the signature changed.
Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(benc)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•