If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

crash nsImapProtocol::ReleaseUrlState

RESOLVED INCOMPLETE

Status

MailNews Core
Networking: IMAP
--
critical
RESOLVED INCOMPLETE
7 years ago
11 months ago

People

(Reporter: wsmwk, Unassigned)

Tracking

({crash})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [rare], crash signature)

crash [@ nsCOMPtr_base::~nsCOMPtr_base() | nsProxyEventObject::~nsProxyEventObject()]

bp-d9093ebb-a4b3-43cf-ae74-acce12100719  v3.1 

0	xpcom_core.dll	nsCOMPtr_base::~nsCOMPtr_base	 objdir-tb/mozilla/xpcom/build/nsCOMPtr.cpp:81
1	xpcom_core.dll	nsProxyEventObject::~nsProxyEventObject	xpcom/proxy/src/nsProxyEventObject.cpp:77
2	xpcom_core.dll	nsProxyEventObject::Release	xpcom/proxy/src/nsProxyEventObject.cpp:116
3	xpcom_core.dll	nsXPTCStubBase::Release	xpcom/reflect/xptcall/src/xptcall.cpp:65
4	xpcom_core.dll	nsRefPtr<nsThread>::assign_assuming_AddRef	objdir-tb/mozilla/dist/include/nsAutoPtr.h:944
5	xpcom_core.dll	nsCOMPtr_base::assign_with_AddRef	objdir-tb/mozilla/xpcom/build/nsCOMPtr.cpp:89
6	thunderbird.exe	nsImapProtocol::ReleaseUrlState	mailnews/imap/src/nsImapProtocol.cpp:993
7	thunderbird.exe	nsImapProtocol::ProcessCurrentURL	mailnews/imap/src/nsImapProtocol.cpp:1795
8	thunderbird.exe	nsImapProtocol::ImapThreadMainLoop	mailnews/imap/src/nsImapProtocol.cpp:1374
9	thunderbird.exe	nsImapProtocol::Run	mailnews/imap/src/nsImapProtocol.cpp:1070
10	xpcom_core.dll	nsThread::ProcessNextEvent	xpcom/threads/nsThread.cpp:527
11	xpcom_core.dll	NS_ProcessNextEvent_P	objdir-tb/mozilla/xpcom/build/nsThreadUtils.cpp:250
12	xpcom_core.dll	nsThread::ThreadFunc	xpcom/threads/nsThread.cpp:254
Component: General → Networking: IMAP
Keywords: crash
Product: Thunderbird → MailNews Core
QA Contact: general → networking.imap
recent example bp-ec7934f5-0a54-4a91-9bd9-319d52110123 v3.1.8pre

all the crashes I checked have nsImapProtocol::ReleaseUrlState on the stacks except ...

bp-1349e58d-2a3c-4c4e-8192-bbb7e2101207 39 days uptime
0	xpcom_core.dll	nsCOMPtr_base::~nsCOMPtr_base	objdir-tb/mozilla/xpcom/build/nsCOMPtr.cpp:81
1	xpcom_core.dll	nsProxyEventObject::~nsProxyEventObject	xpcom/proxy/src/nsProxyEventObject.cpp:77
2	xpcom_core.dll	nsProxyEventObject::Release	xpcom/proxy/src/nsProxyEventObject.cpp:116
3	xpcom_core.dll	nsXPTCStubBase::Release	xpcom/reflect/xptcall/src/xptcall.cpp:65
4	xpcom_core.dll	nsRefPtr<nsThread>::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	nsImapProtocol::TellThreadToDie	mailnews/imap/src/nsImapProtocol.cpp:1272
7	thunderbird.exe	nsImapProtocol::CreateNewLineFromSocket	mailnews/imap/src/nsImapProtocol.cpp:4707
8	thunderbird.exe	nsImapServerResponseParser::GetNextLineForParser	mailnews/imap/src/nsImapServerResponseParser.cpp:128
9	thunderbird.exe	nsIMAPGenericParser::AdvanceToNextLine	mailnews/imap/src/nsIMAPGenericParser.cpp:182
10	thunderbird.exe	nsIMAPGenericParser::AdvanceToNextToken	mailnews/imap/src/nsIMAPGenericParser.cpp:153
11	thunderbird.exe	nsImapServerResponseParser::ParseIMAPServerResponse	mailnews/imap/src/nsImapServerResponseParser.cpp:241
12	thunderbird.exe	nsImapProtocol::ParseIMAPandCheckForNewMail	mailnews/imap/src/nsImapProtocol.cpp:1891 


xref bug 635213
Summary: crash [@ nsCOMPtr_base::~nsCOMPtr_base() | nsProxyEventObject::~nsProxyEventObject()] → crash [@ nsCOMPtr_base::~nsCOMPtr_base() | nsProxyEventObject::~nsProxyEventObject()] - [@ nsImapProtocol::ReleaseUrlState]
(Assignee)

Updated

6 years ago
Crash Signature: [@ nsCOMPtr_base::~nsCOMPtr_base() | nsProxyEventObject::~nsProxyEventObject()] [@ nsImapProtocol::ReleaseUrlState]
current stack version 24.6.0
 nsImapProtocol::ReleaseUrlState(bool) 
bp-be75bb87-8e6c-46b0-8566-9dfa12140803

0 		@0x73202c6e	
1 	xul.dll	nsImapProtocol::ReleaseUrlState(bool)	mailnews/imap/src/nsImapProtocol.cpp
2 	xul.dll	nsImapProtocol::ProcessCurrentURL()	mailnews/imap/src/nsImapProtocol.cpp
3 	xul.dll	nsImapProtocol::ImapThreadMainLoop()	mailnews/imap/src/nsImapProtocol.cpp
4 	xul.dll	nsImapProtocol::Run()	mailnews/imap/src/nsImapProtocol.cpp
Crash Signature: [@ nsCOMPtr_base::~nsCOMPtr_base() | nsProxyEventObject::~nsProxyEventObject()] [@ nsImapProtocol::ReleaseUrlState] → [@ nsCOMPtr_base::~nsCOMPtr_base() | nsProxyEventObject::~nsProxyEventObject()] [@ nsImapProtocol::ReleaseUrlState] [@ nsImapProtocol::ReleaseUrlState(bool)]
Summary: crash [@ nsCOMPtr_base::~nsCOMPtr_base() | nsProxyEventObject::~nsProxyEventObject()] - [@ nsImapProtocol::ReleaseUrlState] → crash nsImapProtocol::ReleaseUrlState
Whiteboard: [rare]

Updated

2 years ago
Crash Signature: [@ nsCOMPtr_base::~nsCOMPtr_base() | nsProxyEventObject::~nsProxyEventObject()] [@ nsImapProtocol::ReleaseUrlState] [@ nsImapProtocol::ReleaseUrlState(bool)] → [@ nsCOMPtr_base::~nsCOMPtr_base() | nsProxyEventObject::~nsProxyEventObject()] [@ nsImapProtocol::ReleaseUrlState] [@ nsImapProtocol::ReleaseUrlState(bool)] [@ nsCOMPtr_base::~nsCOMPtr_base | nsProxyEventObject::~nsProxyEventObject]
(Reporter)

Comment 3

11 months ago
With only 1-2 crashes per week [1] and no STR this does not seem actionable. But I think this became less common in version 45.x compared to 38.x

[1] https://crash-stats.mozilla.com/signature/?signature=nsImapProtocol%3A%3AReleaseUrlState&date=%3E%3D2016-11-02T02%3A16%3A00.000Z&date=%3C2016-11-09T02%3A16%3A00.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_sort=-date&page=1#reports
Status: NEW → RESOLVED
Last Resolved: 11 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.