831305 - crash in mozilla::dom::ContentChild::ProcessingError

Status: RESOLVED INCOMPLETE

(Core :: DOM: Core & HTML, defect)

Description

[Scoobidiver (away)]

It's #5 top crasher in B2G 18.0 with many duplicates.

Frame 	Module 	Signature 	Source
0 	libxul.so 	mozalloc_abort 	mozalloc_abort.cpp:30
1 	libxul.so 	NS_DebugBreak_P 	nsDebugImpl.cpp:423
2 	libxul.so 	mozilla::dom::ContentChild::ProcessingError 	ContentChild.cpp:941
3 	libxul.so 	mozilla::dom::PContentChild::OnProcessingError 	PContentChild.cpp:3128
4 	libxul.so 	mozilla::ipc::AsyncChannel::MaybeHandleError 	AsyncChannel.cpp:611
5 	libxul.so 	mozilla::ipc::AsyncChannel::OnDispatchMessage 	AsyncChannel.cpp:473
6 	libxul.so 	mozilla::ipc::RPCChannel::OnMaybeDequeueOne 	RPCChannel.cpp:402
7 	libxul.so 	RunnableMethod<IPC::ChannelProxy::Context, void , Tuple0>::Run 	tuple.h:383
8 	libxul.so 	mozilla::ipc::RPCChannel::DequeueTask::Run 	RPCChannel.h:425
9 	libxul.so 	MessageLoop::RunTask 	message_loop.cc:333
10 	libxul.so 	MessageLoop::DeferOrRunPendingTask 	message_loop.cc:341
11 	libxul.so 	MessageLoop::DoWork 	message_loop.cc:441
12 	libxul.so 	mozilla::ipc::DoWorkRunnable::Run 	MessagePump.cpp:42
13 	libxul.so 	nsThread::ProcessNextEvent 	nsThread.cpp:620
14 	libxul.so 	NS_ProcessNextEvent_P 	nsThreadUtils.cpp:237
15 	libxul.so 	mozilla::ipc::MessagePump::Run 	MessagePump.cpp:82
16 	libxul.so 	mozilla::ipc::MessagePumpForChildProcess::Run 	MessagePump.cpp:231
17 	libxul.so 	MessageLoop::RunInternal 	message_loop.cc:215
18 	libxul.so 	MessageLoop::Run 	message_loop.cc:208
19 	libxul.so 	nsBaseAppShell::Run 	nsBaseAppShell.cpp:163
20 	libxul.so 	XRE_RunAppShell 	nsEmbedFunctions.cpp:646
21 	libxul.so 	mozilla::ipc::MessagePumpForChildProcess::Run 	MessagePump.cpp:198
22 	libxul.so 	MessageLoop::RunInternal 	message_loop.cc:215
23 	libxul.so 	MessageLoop::Run 	message_loop.cc:208
24 	libxul.so 	XRE_InitChildProcess 	nsEmbedFunctions.cpp:485
25 	plugin-container 	main 	MozillaRuntimeMain.cpp:48 

More reports at:
https://crash-stats.mozilla.com/report/list?signature=mozalloc_abort+|+NS_DebugBreak_P+|+mozilla%3A%3Adom%3A%3AContentChild%3A%3AProcessingError

Comment 1

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

Unfortunately this is an abort because of an IPC protocol error.  There's not much more we can get out of the crash reports.

Comment 2

[Marcia Knous [:marcia]]

No URLs found, removing keyword.

Comment 3

[Alex Keybl [:akeybl]]

(In reply to Chris Jones [:cjones] [:warhammer] from comment #1)
> Unfortunately this is an abort because of an IPC protocol error.  There's
> not much more we can get out of the crash reports.

Given this, and the lack of QA leads, this can't be a 1.0.0 blocker.

Can we make an in-product change to get more info from impacted users? It's possible that this instability issue will be a partner-required blocker in the future.

Comment 4

[Jason Smith [:jsmith]]

Oh and qawanted was called to get steps to reproduce to find the crasher.

Comment 5

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

Is there any tool that can help us out with getting the IPC messages?
I'm guessing that there might be a race condition that's being hit that's causing the issue...

Some of these signature may be legitamate; having said that,  some of these crashes might be on purpose.  I've crashed on purpose (kill -11 <b2g process> and got this signature to test the crash reporting.  There needs to be a way to mark them from being in socorro.

Comment 6

[Tracy Walker [:tracy]]

There haven't been any more reports of this since 3/12

Comment 7

[Jason Smith [:jsmith]]

Closing as incomplete with no evidence of crashes in a month. Reopen if there's something actionable here.

Comment 8

[James Zhang (Spreadtrum)]

please see bug 856076, a lot of new crash report