1465071 - Crash in IPCError-browser | ShutDownKill

Status: RESOLVED DUPLICATE of bug 1219672

(Core :: General, defect)

Description

[Worcester12345]

This bug was filed from the Socorro interface and is
report bp-0f775011-799e-4b6e-b93f-f2b640180529.
=============================================================

Top 10 frames of crashing thread:

0 ntdll.dll ZwWaitForKeyedEvent 
1 ntdll.dll RtlSleepConditionVariableSRW 
2 kernel32.dll SleepConditionVariableSRW 
3 mozglue.dll mozilla::detail::ConditionVariableImpl::wait mozglue/misc/ConditionVariable_windows.cpp:58
4 xul.dll mozilla::CondVar::Wait xpcom/threads/CondVar.h:66
5 xul.dll mozilla::ThreadEventQueue<mozilla::PrioritizedEventQueue<mozilla::LabeledEventQueue> >::GetEvent xpcom/threads/ThreadEventQueue.cpp:155
6 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:994
7 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:519
8 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:125
9 xul.dll mozilla::ipc::MessagePumpForChildProcess::Run ipc/glue/MessagePump.cpp:301

=============================================================

Comment 1

[Anthony Jones (:ajones, :kentuckyfriedtakahe, :k17e)]

Gabriele - what component do you think this bug should go into?

Comment 2

[Gabriele Svelto [:gsvelto]]

I had a look at a few reports and these are all the same: they're content processes being killed by the parent process because they're taking too long to shut down, see the code here [1]. There can be many reasons for that: the content process gets stuck somewhere, or the machine is simply too slow (maybe it's swapping?). Or maybe the timer we use is too short. Anyway it's hard to put these in a specific component.

[1] https://searchfox.org/mozilla-central/rev/b0275bc977ad7fda615ef34b822bba938f2b16fd/dom/ipc/ContentParent.cpp#1411

Comment 5

[Worcester12345]

How do I get from here:
https://crash-stats.mozilla.com/report/index/3b12ef94-90d0-429f-bad8-0add90180914

to get this data put into THIS bug?