Crash in [@ nsImapMockChannel::~nsImapMockChannel]
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
People
(Reporter: wsmwk, Unassigned)
Details
(Keywords: crash, regression, regressionwindow-wanted)
Crash Data
Several crashes starting with build ID 20191008095925 starting Oct 9 up through build ID df2c0ef8-d11e-4b22-8685-83dfa0191016, with none reported for beta. So perhaps we have a nightly regression. https://crash-stats.mozilla.com/signature/?product=Thunderbird&release_channel=%21release&signature=nsImapMockChannel%3A%3A~nsImapMockChannel&date=%3E%3D2019-07-18T06%3A21%3A00.000Z&date=%3C2019-10-18T06%3A21%3A00.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=install_time&_columns=startup_crash&_sort=-date&page=1#graphs
So far all Linux and win10
bp-df2c0ef8-d11e-4b22-8685-83dfa0191016 Linux
Top 10 frames of crashing thread:
0 libxul.so nsImapMockChannel::~nsImapMockChannel comm/mailnews/imap/src/nsImapProtocol.cpp:8467
1 libxul.so nsImapMockChannel::~nsImapMockChannel comm/mailnews/imap/src/nsImapProtocol.cpp:8463
2 libxul.so <name omitted> comm/mailnews/imap/src/nsImapProtocol.cpp:8450
3 libxul.so nsImapProtocol::RetryUrl comm/mailnews/imap/src/nsImapProtocol.cpp:1894
4 libxul.so nsImapProtocol::ProcessCurrentURL comm/mailnews/imap/src/nsImapProtocol.cpp
5 libxul.so nsImapProtocol::ImapThreadMainLoop comm/mailnews/imap/src/nsImapProtocol.cpp:1418
6 libxul.so nsImapProtocol::Run comm/mailnews/imap/src/nsImapProtocol.cpp:1100
7 libxul.so non-virtual thunk to nsImapProtocol::Run comm/mailnews/imap/src/nsImapProtocol.cpp
8 libxul.so nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1225
9 libxul.so NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:486
|
Reporter | |
Comment 1•6 years ago
|
||
Or it could be the related to crashes occuring in release and some nightly users only recently hit the steps needed. I haven't attempted to correlate stacks, and we don't have an identified reporter as far as I know,
|
||
Comment 2•6 years ago
|
||
As I said before: Always look at the crash reason first:
MOZ_CRASH Reason (Sanitized)
MOZ_DIAGNOSTIC_ASSERT(NS_IsMainThread()) (should only access mock channel on ui thread)
So yes, we landed a crasher patch to fix the threading mess in bug 1586494.
Description
•