Closed
Bug 637338
Opened 15 years ago
Closed 7 years ago
crash @ nsMsgProtocol::~nsMsgProtocol
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: wsmwk, Unassigned)
References
Details
(Keywords: crash)
Crash Data
crash [@ nsCOMPtr_base::~nsCOMPtr_base() | nsMsgProtocol::~nsMsgProtocol()]
bp-bb94781a-ebbe-423c-a7f6-4dd6a2110225
EXCEPTION_ACCESS_VIOLATION_READ
0x9
0 xpcom_core.dll nsCOMPtr_base::~nsCOMPtr_base objdir-tb/mozilla/xpcom/build/nsCOMPtr.cpp:81
1 thunderbird.exe nsMsgProtocol::~nsMsgProtocol mailnews/base/util/nsMsgProtocol.cpp:116
2 thunderbird.exe nsPop3Protocol::`vector deleting destructor'
3 thunderbird.exe nsMsgProtocol::Release mailnews/base/util/nsMsgProtocol.cpp:71
4 xpcom_core.dll nsCOMPtr_base::assign_assuming_AddRef objdir-tb/mozilla/dist/include/nsCOMPtr.h:456
5 xpcom_core.dll nsCOMPtr_base::assign_with_AddRef objdir-tb/mozilla/xpcom/build/nsCOMPtr.cpp:89
6 thunderbird.exe nsSHEntry::SetURI mailnews/local/src/nsPop3IncomingServer.cpp:644
7 thunderbird.exe nsPop3Protocol::LoadUrl mailnews/local/src/nsPop3Protocol.cpp:1081
8 thunderbird.exe nsPop3Service::RunPopUrl mailnews/local/src/nsPop3Service.cpp:293
9 thunderbird.exe nsPop3Service::GetMail mailnews/local/src/nsPop3Service.cpp:165
10 thunderbird.exe nsPop3Service::GetNewMail mailnews/local/src/nsPop3Service.cpp:104
11 thunderbird.exe nsPop3IncomingServer::PerformBiff mailnews/local/src/nsPop3IncomingServer.cpp:436
12 thunderbird.exe nsMsgBiffManager::PerformBiff mailnews/base/src/nsMsgBiffManager.cpp:343
bp-0e8d0888-435a-40bd-aecf-c8f882110223 (gnbowen)
EXCEPTION_ACCESS_VIOLATION_READ
0x1
0 xpcom_core.dll nsCOMPtr_base::~nsCOMPtr_base objdir-tb/mozilla/xpcom/build/nsCOMPtr.cpp:81
1 thunderbird.exe nsMsgProtocol::~nsMsgProtocol mailnews/base/util/nsMsgProtocol.cpp:116
2 thunderbird.exe nsPop3Protocol::`vector deleting destructor'
3 thunderbird.exe nsMsgProtocol::Release mailnews/base/util/nsMsgProtocol.cpp:71
4 xpcom_core.dll nsProxyReleaseEvent::Run objdir-tb/mozilla/xpcom/build/nsProxyRelease.cpp:52
5 xpcom_core.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:527
| Assignee | ||
Updated•15 years ago
|
Crash Signature: [@ nsCOMPtr_base::~nsCOMPtr_base() | nsMsgProtocol::~nsMsgProtocol()]
| Reporter | ||
Updated•14 years ago
|
Crash Signature: [@ nsCOMPtr_base::~nsCOMPtr_base() | nsMsgProtocol::~nsMsgProtocol()] → [@ nsCOMPtr_base::~nsCOMPtr_base() | nsMsgProtocol::~nsMsgProtocol()]
[@ nsRefPtr<nsTypedSelection>::~nsRefPtr<nsTypedSelection>() | nsMsgProtocol::~nsMsgProtocol()]
[@ nsCOMPtr_base::~nsCOMPtr_base | nsMsgProtocol::~nsMsgProtocol
nsMsgProtocol::~nsMsg…
| Reporter | ||
Comment 1•13 years ago
|
||
current signatures are
nsMsgProtocol::~nsMsgProtocol Mac
nsMsgProtocol::~nsMsgProtocol() windows bp-d3df930f-8749-41a6-b5ca-be44d2121118
0 xul.dll nsMsgProtocol::~nsMsgProtocol mailnews/base/util/nsMsgProtocol.cpp:87
1 xul.dll nsMsgProtocol::`scalar deleting destructor'
2 xul.dll nsNotifyAddrListener::Release js/xpconnect/src/XPCComponents.cpp:2199
3 xul.dll nsProxyReleaseEvent::Run parser/html/nsHtml5RefPtr.h:22
4 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:624
5 xul.dll NS_ProcessNextEvent_P objdir-tb/mozilla/xpcom/build/nsThreadUtils.cpp:217
slightly different stacks:
bp-d8aa7b1a-98da-46cd-b3e3-92ffe2121114
bp-3b9f1a78-62f6-4745-be85-6af592121114
0 xul.dll nsMsgProtocol::~nsMsgProtocol mailnews/base/util/nsMsgProtocol.cpp:87
1 xul.dll nsPop3Protocol::`scalar deleting destructor'
2 xul.dll nsNotifyAddrListener::Release js/xpconnect/src/XPCComponents.cpp:2199
3 xul.dll nsPop3IncomingServer::CloseCachedConnections mailnews/local/src/nsPop3IncomingServer.cpp:586
4 xul.dll nsMsgIncomingServer::Shutdown mailnews/base/util/nsMsgIncomingServer.cpp:207
Crash Signature: [@ nsCOMPtr_base::~nsCOMPtr_base() | nsMsgProtocol::~nsMsgProtocol()]
[@ nsRefPtr<nsTypedSelection>::~nsRefPtr<nsTypedSelection>() | nsMsgProtocol::~nsMsgProtocol()]
[@ nsCOMPtr_base::~nsCOMPtr_base | nsMsgProtocol::~nsMsgProtocol
nsMsgProtocol::~nsMsg… → [@ nsMsgProtocol::~nsMsgProtocol() ]
[@ nsMsgProtocol::~nsMsgProtocol]
[@ nsCOMPtr_base::~nsCOMPtr_base() | nsMsgProtocol::~nsMsgProtocol()]
[@ nsRefPtr<nsTypedSelection>::~nsRefPtr<nsTypedSelection>() | nsMsgProtocol::~nsMsgProtocol()]
[@ nsCOMPtr_ba…
Summary: crash [@ nsCOMPtr_base::~nsCOMPtr_base() | nsMsgProtocol::~nsMsgProtocol()] → crash [@ nsMsgProtocol::~nsMsgProtocol()]
| Reporter | ||
Comment 2•13 years ago
|
||
as noted in bug 673438 comment 41, Larry Chen was seeing this signature, and bug 673438's. But Larry is no longer crashing.
a recent example
bp-d04dd858-6a6f-41ef-aaba-329c92130702
0 xul.dll nsMsgProtocol::~nsMsgProtocol mailnews/base/util/nsMsgProtocol.cpp:87
1 xul.dll nsMsgProtocol::`vector deleting destructor'
2 xul.dll nsNotifyAddrListener::Release netwerk/system/win32/nsNotifyAddrListener.cpp:58
3 xul.dll nsProxyReleaseEvent::Run parser/html/nsHtml5RefPtr.h:22
4 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:624
5 xul.dll NS_ProcessNextEvent_P objdir-tb/mozilla/xpcom/build/nsThreadUtils.cpp:220
hg@0 86 nsMsgProtocol::~nsMsgProtocol()
hg@0 87{}
Depends on: 673438
Comment 3•11 years ago
|
||
Removing myslef on all the bugs I'm cced on. Please NI me if you need something on MailNews Core bugs from me.
Updated•11 years ago
|
Crash Signature: nsCOMPtr_base::~nsCOMPtr_base | nsMsgProtocol::~nsMsgProtocol
nsMsgProtocol::~nsMsgProtocol()] → nsCOMPtr_base::~nsCOMPtr_base | nsMsgProtocol::~nsMsgProtocol
nsMsgProtocol::~nsMsgProtocol()]
[@ nsCOMPtr_base::~nsCOMPtr_base | nsMsgProtocol::~nsMsgProtocol]
[@ nsRefPtr<T>::~nsRefPtr<T> | nsMsgProtocol::~nsMsgProtocol]
[@ nsCOMPtr_base::~nsCOMPtr…
Comment 4•9 years ago
|
||
I'm marking this bug as WORKSFORME as bug crashlog signature didn't appear from a long time (over half year).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Comment 5•9 years ago
|
||
Ups, my bad and due to ( bug #1348631 ) looks like there are sill crashes, so reopening.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
| Reporter | ||
Comment 6•9 years ago
|
||
Thanks for rechecking.
There are no crashes for 45.8.0, which is the most recent release. So closing.
https://crash-stats.mozilla.com/search/?signature=~nsMsgProtocol%3A%3A~nsMsgProtocol&product=Thunderbird&date=%3E%3D2016-12-20T13%3A42%3A34.000Z&date=%3C2017-03-20T13%3A42%3A34.000Z&_sort=-date&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#crash-reports
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 7•8 years ago
|
||
But there have been version 52 crashes. Unclear if same or different issue
bp-f0f89514-9d24-44fa-8fec-4bb830180806
typical stack
Frame Module Signature Source
0 xul.dll nsMsgProtocol::~nsMsgProtocol() C:/builds/moz2_slave/tb-rel-c-esr52-w32_bld-0000000/build/mailnews/base/util/nsMsgProtocol.cpp:89
1 xul.dll nsMsgFilePostHelper::`scalar deleting destructor'(unsigned int)
2 xul.dll nsBufferedStream::Release() netwerk/base/nsBufferedStreams.cpp:65
3 xul.dll nsInputStreamPump::OnStateStop() netwerk/base/nsInputStreamPump.cpp:717
4 xul.dll nsInputStreamPump::OnInputStreamReady(nsIAsyncInputStream*) netwerk/base/nsInputStreamPump.cpp:433
5 xul.dll nsInputStreamReadyEvent::Run() xpcom/io/nsStreamUtils.cpp:95
Status: RESOLVED → REOPENED
Flags: needinfo?(m_kato)
Resolution: WORKSFORME → ---
Comment 8•7 years ago
|
||
It touches destroyed nsMsgProtocol, but I don't know since root cause is unclear.
Flags: needinfo?(m_kato)
| Reporter | ||
Comment 9•7 years ago
|
||
Thanks for looking.
No crashes so far for version 60, so => WFM
Status: REOPENED → RESOLVED
Crash Signature: [@ nsMsgProtocol::~nsMsgProtocol() ]
[@ nsMsgProtocol::~nsMsgProtocol]
[@ nsCOMPtr_base::~nsCOMPtr_base() | nsMsgProtocol::~nsMsgProtocol()]
[@ nsRefPtr<nsTypedSelection>::~nsRefPtr<nsTypedSelection>() | nsMsgProtocol::~nsMsgProtocol()]
[@ nsCOMPtr_ba… → [@ nsMsgProtocol::~nsMsgProtocol]
Closed: 9 years ago → 7 years ago
Resolution: --- → WORKSFORME
Summary: crash [@ nsMsgProtocol::~nsMsgProtocol()] → crash @ nsMsgProtocol::~nsMsgProtocol
You need to log in
before you can comment on or make changes to this bug.
Description
•