677416 - Crash [@ NS_ProcessNextEvent_P ]

Status: RESOLVED INCOMPLETE

(Core :: Layout, defect)

Description

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

https://crash-stats.mozilla.com/report/index/3f18a874-1825-4e29-b9bb-b41632110802

Frame 	Module 	Signature [Expand] 	Source
0 		@0x6ac41400 	
1 	libxul.so 	NS_ProcessNextEvent_P 	obj-firefox/xpcom/build/nsThreadUtils.cpp:245
2 	libxul.so 	mozilla::ipc::MessagePump::Run 	ipc/glue/MessagePump.cpp:111
3 	libxul.so 	mozilla::ipc::MessagePumpForChildProcess::Run 	ipc/glue/MessagePump.cpp:230
4 	libxul.so 	MessageLoop::RunInternal 	ipc/chromium/src/base/message_loop.cc:219
5 	libxul.so 	MessageLoop::Run 	ipc/chromium/src/base/message_loop.cc:511
6 	libxul.so 	nsBaseAppShell::Run 	widget/src/xpwidgets/nsBaseAppShell.cpp:191
7 	libxul.so 	XRE_RunAppShell 	toolkit/xre/nsEmbedFunctions.cpp:671
8 	libxul.so 	mozilla::ipc::MessagePumpForChildProcess::Run 	ipc/glue/MessagePump.cpp:222
9 	libxul.so 	MessageLoop::RunInternal 	ipc/chromium/src/base/message_loop.cc:219
10 	libxul.so 	MessageLoop::Run 	ipc/chromium/src/base/message_loop.cc:511
11 	libxul.so 	XRE_InitChildProcess 	toolkit/xre/nsEmbedFunctions.cpp:514
12 	libmozutils.so 	ChildProcessInit 	other-licenses/android/APKOpen.cpp:801
13 	plugin-container 	main 	ipc/app/MozillaRuntimeMainAndroid.cpp:69
14 	libc.so 	libc.so@0x14cbc

Only stack listed :
https://crash-stats.mozilla.com/report/list?range_value=7&range_unit=days&date=2011-08-08%2001%3A00%3A00&signature=NS_ProcessNextEvent_P&version=Fennec%3A7.0a2

Related bug 394014?

Comment 1

[Wayne Mery (:wsmwk)]

there are still crashes, but somewhat rare

https://crash-stats.mozilla.com/query/query?product=Fennec&product=FennecAndroid&version=ALL%3AALL&range_value=3&range_unit=weeks&date=05%2F07%2F2013+14%3A14%3A15&query_search=signature&query_type=contains&query=NS_ProcessNextEvent_P&reason=&build_id=&process_type=any&hang_type=any&do_query=1

including signature NS_ProcessNextEvent_P(nsIThread*, bool)

Comment 2

[Mats Palmgren (inactive)]

NS_ProcessNextEvent_P seems to have been removed, so I think this bug will be filed
under a different signature if it still occurs.