922196 - crash in nsBaseAppShell::DoProcessNextNativeEvent

Status: RESOLVED WONTFIX

(Core :: Widget, defect, P4)

Description

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

This bug was filed from the Socorro interface and is 
report bp-f9911535-fb87-4f1f-84b3-b88232130926.
=============================================================
Frame 	Module 	Signature 	Source
0 	libc.so 	libc.so@0xd604 	
1 	libxul.so 	nsBaseAppShell::DoProcessNextNativeEvent(bool, unsigned int) 	widget/xpwidgets/nsBaseAppShell.cpp
2 	libxul.so 	nsBaseAppShell::OnProcessNextEvent(nsIThreadInternal*, bool, unsigned int) 	widget/xpwidgets/nsBaseAppShell.cpp
3 	libxul.so 	nsThread::ProcessNextEvent(bool, bool*) 	xpcom/threads/nsThread.cpp
4 	libxul.so 	NS_ProcessNextEvent(nsIThread*, bool) 	xpcom/glue/nsThreadUtils.cpp
5 	libxul.so 	mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) 	ipc/glue/MessagePump.cpp
6 	libxul.so 	mozilla::ipc::MessagePumpForChildProcess::Run(base::MessagePump::Delegate*) 	ipc/glue/MessagePump.cpp
7 	libxul.so 	MessageLoop::RunInternal() 	ipc/chromium/src/base/message_loop.cc
8 	libxul.so 	MessageLoop::Run() 	ipc/chromium/src/base/message_loop.cc
9 	libxul.so 	nsBaseAppShell::Run() 	widget/xpwidgets/nsBaseAppShell.cpp
10 	libxul.so 	XRE_RunAppShell 	toolkit/xre/nsEmbedFunctions.cpp
11 	libxul.so 	mozilla::ipc::MessagePumpForChildProcess::Run(base::MessagePump::Delegate*) 	ipc/glue/MessagePump.cpp
12 	libxul.so 	MessageLoop::RunInternal() 	ipc/chromium/src/base/message_loop.cc
13 	libxul.so 	MessageLoop::Run() 	ipc/chromium/src/base/message_loop.cc
14 	libxul.so 	XRE_InitChildProcess 	toolkit/xre/nsEmbedFunctions.cpp
15 	plugin-container 	main 	ipc/app/MozillaRuntimeMain.cpp
16 	libc.so 	__libc_init 	bionic/libc/bionic/libc_init_dynamic.c
17 		@0xb00045a9

More crashes: https://crash-stats.mozilla.com/report/list?product=B2G&signature=nsBaseAppShell%3A%3ADoProcessNextNativeEvent%28bool%2C+unsigned+int%29

Note : this could be a purposeful crash, kill -11 would cause this crash to occur.  Need to figure out how to flag crashes on purpose.

Comment 1

[Kyle Wooten]

Thanks!

Comment 2

[Benjamin Smedberg]

Why would anyone kill -11 a process? Kill -6 (SIGABRT) is what I'd expect if we were intentionally aborting processes.

Also the crash address is 0x89b which makes me think this isn't an intentional crash anyway.

Comment 3

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

To test the crash UI.  Hrm a -6 also shows the crash ui.  Interesting; these are the crashes that I received using a -6:

bp-0add4203-aaff-465d-bb83-e7fc52140121
bp-bc507892-5ba9-487b-9317-52ebb2140121
bp-db63c1ff-9afd-4614-9cb0-a7e842140121

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

Crash volume for signature 'nsBaseAppShell::DoProcessNextNativeEvent':
 - nightly (version 53): 0 crashes from 2016-11-14.
 - aurora  (version 52): 1 crash from 2016-11-14.
 - beta    (version 51): 20 crashes from 2016-11-14.
 - release (version 50): 1045 crashes from 2016-11-01.
 - esr     (version 45): 5 crashes from 2016-07-06.

Crash volume on the last weeks (Week N is from 01-02 to 01-08):
            W. N-1  W. N-2  W. N-3  W. N-4  W. N-5  W. N-6  W. N-7
 - nightly       0       0       0       0       0       0       0
 - aurora        0       0       1       0       0       0       0
 - beta          1       0       3       6       3       7       1
 - release       4       9      17      16     363     634       1
 - esr           1       0       0       0       0       0       0

Affected platform: Windows

Crash rank on the last 7 days:
           Browser   Content   Plugin
 - nightly
 - aurora  #5018
 - beta    #2717     #4033
 - release #1100     #142
 - esr

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.