608378 - Crash in [@ NS_InvokeByIndex_P ] with Bandoo 5.0

Status: RESOLVED DUPLICATE of bug 629634

(Core :: XPConnect, defect)

Description

[Marcia Knous [:marcia]]

Seen while reviewing nightly crash data. http://tinyurl.com/289s9tg links to the recent crashes, which are all Win XP. Most are startup crashes on the trunk but this crash happens on the other branches as well. The link to those crashes is here: http://tinyurl.com/2b9xwkr.  Several of the branch crash reports mention Comcast.

Frame 	Module 	Signature 	Source
0 		@0x12085e70 	
1 	xul.dll 	NS_InvokeByIndex_P 	xpcom/reflect/xptcall/src/md/win32/xptcinvoke.cpp:102
2 	xul.dll 	XPCWrappedNative::CallMethod 	js/src/xpconnect/src/xpcwrappednative.cpp:2285
3 	xul.dll 	XPC_WN_CallMethod 	js/src/xpconnect/src/xpcwrappednativejsops.cpp:1631
4 	mozjs.dll 	js::Interpret 	js/src/jsinterp.cpp:4702
5 	mozjs.dll 	js::RunScript 	js/src/jsinterp.cpp:638
6 	mozjs.dll 	js::Invoke 	js/src/jsinterp.cpp:741
7 	mozjs.dll 	js::ExternalInvoke 	js/src/jsinterp.cpp:856
8 	mozjs.dll 	JS_CallFunctionValue 	js/src/jsapi.cpp:4933
9 	xul.dll 	nsXBLProtoImplAnonymousMethod::Execute 	content/xbl/src/nsXBLProtoImplMethod.cpp:341
10 	xul.dll 	nsBindingManager::ProcessAttachedQueue 	content/xbl/src/nsBindingManager.cpp:1020
11 	xul.dll 	PresShell::InitialReflow 	layout/base/nsPresShell.cpp:2712
12 	xul.dll 	nsXULDocument::StartLayout 	content/xul/document/src/nsXULDocument.cpp:2016
13 	xul.dll 	nsXULDocument::DoneWalking 	content/xul/document/src/nsXULDocument.cpp:3166
14 	xul.dll 	nsXULDocument::ResumeWalk 	content/xul/document/src/nsXULDocument.cpp:3115
15 	mozcrt19.dll 	free 	obj-firefox/memory/jemalloc/crtsrc/jemalloc.c:6121
16 	xul.dll 	nsXULDocument::OnStreamComplete 	content/xul/document/src/nsXULDocument.cpp:3576
17 	xul.dll 	nsStreamLoader::OnStopRequest 	netwerk/base/src/nsStreamLoader.cpp:125
18 	xul.dll 	nsJARChannel::OnStopRequest 	modules/libjar/nsJARChannel.cpp:906
19 	xul.dll 	nsInputStreamPump::OnStateStop 	netwerk/base/src/nsInputStreamPump.cpp:578
20 	xul.dll 	nsInputStreamPump::OnInputStreamReady 	netwerk/base/src/nsInputStreamPump.cpp:403
21 	xul.dll 	nsInputStreamReadyEvent::Run 	xpcom/io/nsStreamUtils.cpp:112
22 	xul.dll 	nsThread::ProcessNextEvent 	xpcom/threads/nsThread.cpp:609
23 	xul.dll 	mozilla::ipc::MessagePump::Run 	ipc/glue/MessagePump.cpp:110
24 	xul.dll 	xul.dll@0xb004db 	
25 	xul.dll 	MessageLoop::RunHandler 	ipc/chromium/src/base/message_loop.cc:202
26 	xul.dll 	_SEH_epilog4 	
27 	xul.dll 	MessageLoop::Run 	ipc/chromium/src/base/message_loop.cc:176
28 	xul.dll 	nsBaseAppShell::Run 	widget/src/xpwidgets/nsBaseAppShell.cpp:181
29 	xul.dll 	xul.dll@0xb004db 	
30 	xul.dll 	nsAppShell::Run 	widget/src/windows/nsAppShell.cpp:243
31 	nss3.dll 	pkix_pl_CertNameConstraints_ToString 	security/nss/lib/libpkix/pkix_pl_nss/pki/pkix_pl_nameconstraints.c:539

Comment 1

[chris hofmann]

I think that these 4.0b8pre crashes from yesterday are all dups of one or two real incidences.

https://crash-stats.mozilla.com/report/list?product=Firefox&branch=2.0&platform=windows&build_id=20101029041804&query_search=signature&query_type=exact&query=&date=10%2F29%2F2010%2013%3A33%3A51&range_value=30&range_unit=days&hang_type=any&process_type=all&plugin_field=&plugin_query_type=&plugin_query=&do_query=1&signature=NS_InvokeByIndex_P&missing_sig=&page=1#reports

https://crash-stats.mozilla.com/report/index/d684e45b-a137-467d-bbeb-1dac72101029

might be the initial incident at 09:33 , followed by 3 more reports withing the same minute, then another series of 7 reports at 09:49

Comment 2

[chris hofmann]

the major shipping release problem is very real though...

almost a thousand crashes per day on releases that have over a million users,
it just doesn't seem to appear on trunk very often so if it continues there it would be news.

         NS_InvokeByIndex_P

date     total    breakdown by build
         crashes  count build, count build, ...

20101028 969  	473 3.6.112010101211, 
        		308 3.6.122010102621, 	49 3.6.102010091412, 
        		31 3.6.82010072215, 	19 3.6.32010040108, 
        		15 3.0.192010031422, 	13 3.6.62010062523, 
        		11 3.5.142010100117, 	9 3.62010011514, 
        		7 3.6.92010082415, 	4 4.0b62010091408, 
        		4 3.6.72010071313, 	4 3.6.42010061114, 
        		3 3.5.152010102620, 	3 3.5.132010091413, 
        		1 4.0b32010080519, 	1 3.7a52010061006, 
        		1 3.6b52009120414, 	1 3.6b42009112421, 
        		1 3.6b22009110818, 	1 3.6.72010070102, 
        		1 3.6.42010051314, 	1 3.6.22010031607, 
        		1 3.6.112010101210, 	1 3.5.72009122116, 
        		1 3.5.52009110215, 	1 3.5.32009082410, 
        		1 3.5.22009072922, 	1 3.52009061622, 
        		1 3.1b32009030515, 	1 3.0.52008120122,

Comment 3

[chris hofmann]

#14 in 3.6.13 with 80-90 million users
#37 in 3.6.12 with around 2 million users
and #272 - #283 in 4.0b9 with around 600k users and b8 with 1.2million users

so it will be interesting to see if there is a fix working here, or if we need to get over 10million users for this to move higher in the ranking.

Comment 4

[Scoobidiver (away)]

Here are:
* 4.0b11 extension correlations:
94% (115/122) vs.   3% (1277/41916) [e-mail] (5.0)
* 3.6.13 extension correlations:
97% (445/460) vs.   3% (4381/155839) [e-mail] (5.0)

It will be fixed by the Bandoo 5.0 block-listing in bug 629634, at least for 4.0b11.

Comment 6

[Scoobidiver (away)]

I mark it as a dupe of bug 629634.
If you see this crash signature with another extension, file a new bug.