Crash in [@ mozilla::dom::ContentChild::RecvConstructBrowser] at MOZ_DIAGNOSTIC_ASSERT(!IsShuttingDown())
Categories
(Core :: DOM: Content Processes, defect)
Tracking
()
People
(Reporter: mccr8, Unassigned)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/93754988-a4ea-463b-8294-2dc390211208
MOZ_CRASH Reason: MOZ_DIAGNOSTIC_ASSERT(!IsShuttingDown())
Top 10 frames of crashing thread:
0 XUL mozilla::dom::ContentChild::RecvConstructBrowser dom/ipc/ContentChild.cpp:1766
1 XUL mozilla::dom::PContentChild::OnMessageReceived ipc/ipdl/PContentChild.cpp:8362
2 XUL mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:1968
3 XUL mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:1855
4 XUL mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal xpcom/threads/TaskController.cpp:771
5 XUL mozilla::TaskController::ProcessPendingMTTask xpcom/threads/TaskController.cpp:391
6 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1183
7 XUL nsThread::Dispatch xpcom/threads/nsThread.cpp:673
8 XUL mozilla::ChildProfilerController::ShutdownAndMaybeGrabShutdownProfileFirst tools/profiler/gecko/ChildProfilerController.cpp:98
9 XUL mozilla::ChildProfilerController::GrabShutdownProfileAndShutdown tools/profiler/gecko/ChildProfilerController.cpp:58
Very low volume crash, but it is a release assert so maybe there's something interesting here.
In all 3 crashes, I see us spinning a nested event loop in ChildProfilerController::ShutdownAndMaybeGrabShutdownProfileFirst() and then we get another message.
Updated•4 years ago
|
Comment 1•4 years ago
|
||
That assertion has been introduced by D121687. Should we add an early return here instead?
Comment 2•4 years ago
|
||
or rather, the assertion has been there for awhile, but it was made diagnostic.
But I think this can happen only if the parent process sends ConstructBrowser after sending Shutdown to the relevant child process.
And we shouldn't do that.
We could add some diagnostic assertions to parent process to hint why we construct browsers so late.
Comment 3•4 years ago
|
||
(In reply to Olli Pettay [:smaug] from comment #2)
or rather, the assertion has been there for awhile, but it was made diagnostic.
But I think this can happen only if the parent process sends ConstructBrowser after sending Shutdown to the relevant child process.
And we shouldn't do that.
We could add some diagnostic assertions to parent process to hint why we construct browsers so late.
OK, but since then should we mitigate this in release builds?
Comment 4•4 years ago
|
||
This isn't in release builds, right?
It is just MOZ_DIAGNOSTIC_ASSERT
Comment 5•4 years ago
|
||
Yes but as you said we shouldn't do that at all, so I would have assumed returning early would prevent us from further weirdnesses? But yes, we should analyse the callers for sure.
Comment 6•4 years ago
|
||
oh, I see, my bad. I meant that the assertion is reasonable and we should fix the sender of the message.
Comment 7•3 years ago
|
||
Closing because no crashes reported for 12 weeks.
Description
•