859246 - crash in nsMsgCompose::Initialize

Status: RESOLVED WORKSFORME

(Thunderbird :: Message Compose Window, defect)

Description

[Ludovic Hirlimann [:Usul]]

This bug was filed from the Socorro interface and is 
report bp-fc39e054-a0dd-4230-9fc0-2a4b52130405 .
============================================================= 
Also happens on MacOS -> All

0 	libxul.so 	nsMsgCompose::Initialize 	mailnews/compose/src/nsMsgCompose.cpp:897
1 	libxul.so 	matchPrefEntry 	modules/libpref/src/prefapi.cpp:71
2 	libxul.so 	SearchTable 	objdir-tb/mozilla/xpcom/build/pldhash.cpp:401
3 	libxul.so 	pref_ValueChanged 	modules/libpref/src/prefapi.cpp:702
4 	libxul.so 	mozilla::Preferences::Release 	modules/libpref/src/Preferences.cpp:330
5 	libxul.so 	PREF_GetBoolPref 	modules/libpref/src/prefapi.cpp:541
6 	libxul.so 	nsMsgCompose::Release 	mailnews/compose/src/nsMsgCompose.cpp:184
7 	libxul.so 	mozilla::GenericFactory::Release 	objdir-tb/mozilla/xpcom/build/GenericFactory.cpp:10
8 	libxul.so 	nsComponentManagerImpl::CreateInstanceByContractID 	objdir-tb/mozilla/dist/include/nsCOMPtr.h:453
9 	libxul.so 	nsGlobalWindow::QueryInterface 	dom/base/nsGlobalWindow.cpp:1525
10 	libxul.so 	nsCreateInstanceByContractID::operator const 	objdir-tb/mozilla/xpcom/build/nsComponentManagerUtils.cpp:178
11 	libxul.so 	nsMsgComposeService::InitCompose 	mailnews/compose/src/nsMsgComposeService.cpp:737
12 	libxul.so 	NS_InvokeByIndex 	xpcom/reflect/xptcall/src/md/unix/xptcinvoke_x86_64_unix.cpp:164
13 	libxul.so 	xptiInterfaceEntry::GetEntryForParam 	xpcom/reflect/xptinfo/src/xptiInterfaceInfo.cpp:293
14 	libxul.so 	XPCWrappedNative::CallMethod 	js/xpconnect/src/XPCWrappedNative.cpp:2953
15 	gtk20-properties.mo 	gtk20-properties.mo@0x1a292 	
16 	libxul.so 	JSScript::makeAnalysis 	js/src/jsinfer.cpp:5971
17 	libxul.so 	js::InvokeKernel 	js/src/vm/Stack.h:1826
18 	libxul.so 	xpc::WrapperFactory::PrepareForWrapping 	js/xpconnect/wrappers/WrapperFactory.cpp:166
19 	ld-2.17.so 	ld-2.17.so@0x121f 	
20 	libxul.so 	js::UnwrapObjectChecked 	js/src/jswrapper.cpp:92
21 	libxul.so 	XPCCallContext::Init 	js/xpconnect/src/xpcprivate.h:2715
22 	libxul.so 	XPCCallContext::XPCCallContext 	js/xpconnect/src/XPCCallContext.cpp:37
23 	libxul.so 	XPC_WN_CallMethod 	js/xpconnect/src/XPCWrappedNativeJSOps.cpp:1459

Comment 1

[Wayne Mery (:wsmwk)]

crash comments make it clear the increased crash rate is related to our friends - bug 525444 and bug 858014

And also Seamonkey https://crash-stats.mozilla.com/report/list?product=SeaMonkey&query_search=signature&query_type=exact&query=nsMsgCompose%3A%3AInitialize%28nsIMsgComposeParams*%2C%20nsIDOMWindow*%2C%20nsIDocShell*%29&reason_type=contains&date=04%2F08%2F2013%2011%3A26%3A53&range_value=2&range_unit=weeks&hang_type=any&process_type=any&do_query=1&admin=1&signature=nsMsgCompose%3A%3AInitialize%28nsIMsgComposeParams*%2C%20nsIDOMWindow*%2C%20nsIDocShell*%29

Somewhat interesting that none of the trunk crashes are windows.
 

However, the crash is not new, and not limited to linux+mac nor trunk.
bp-eaab5a93-1621-427f-b50f-d95b72121231 TB17.0
bp-6675319c-888c-4a94-b6a3-4584c2130114 TB17.0.2
bp-09206203-7f89-4d26-9cb9-ce4532130213 TB17.0.2
bp-267705b6-a27a-44cb-98ce-5c1552130226 TB17.0.3

Comment 2

[Mark Banner (:standard8)]

(In reply to Wayne Mery (:wsmwk) from comment #1)
> crash comments make it clear the increased crash rate is related to our
> friends - bug 525444 and bug 858014
> 
> And also Seamonkey
> https://crash-stats.mozilla.com/report/
> list?product=SeaMonkey&query_search=signature&query_type=exact&query=nsMsgCom
> pose%3A%3AInitialize%28nsIMsgComposeParams*%2C%20nsIDOMWindow*%2C%20nsIDocShe
> ll*%29&reason_type=contains&date=04%2F08%2F2013%2011%3A26%3A53&range_value=2&
> range_unit=weeks&hang_type=any&process_type=any&do_query=1&admin=1&signature=
> nsMsgCompose%3A%3AInitialize%28nsIMsgComposeParams*%2C%20nsIDOMWindow*%2C%20n
> sIDocShell*%29
> 
> Somewhat interesting that none of the trunk crashes are windows.

Windows nightly builds have been busted for the entire period bug 858014 has been in effect. I suspect this particular crash will be fixed now we've fixed the underlying issue.

> However, the crash is not new, and not limited to linux+mac nor trunk.
> bp-eaab5a93-1621-427f-b50f-d95b72121231 TB17.0
> bp-6675319c-888c-4a94-b6a3-4584c2130114 TB17.0.2
> bp-09206203-7f89-4d26-9cb9-ce4532130213 TB17.0.2
> bp-267705b6-a27a-44cb-98ce-5c1552130226 TB17.0.3

There's possibility for a crash there although I don't see why, but these aren't going to be related to bug 858014/bug 525444 in any way.

Comment 3

[Tony Mechelynck [:tonymec]]

(In reply to Mark Banner (:standard8) from comment #2)
[...]
> > Somewhat interesting that none of the trunk crashes are windows.
[...]

That is probably an artefact (by grid truncation) of how you displayed the results. Sort the "Reports" table for that SeaMonkey crash list, fist by OS reversed (minor key W→M→L), then by Version, and you'll se quite a number of 2.20a1 crashes on Windows.

Comment 4

[Wayne Mery (:wsmwk)]

gone from crash-stats after aug 10 for trunk

Comment 5

[Tony Mechelynck [:tonymec]]

Resolving WORKSFORME based on comment #4.

Feel free to REOPEN (with a bp-something crash dump, of course) if you see this bug in a recent Daily (Thunderbird 29.0a1) or even Aurora (28.0a2) version of Thunderbird.