Crash in [@ mozilla::dom::WindowGlobalParent::Init]
Categories
(Core :: DOM: Content Processes, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox73 | --- | unaffected |
firefox74 | --- | unaffected |
firefox75 | --- | fixed |
People
(Reporter: calixte, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: crash, regression)
Crash Data
This bug is for crash report bp-97fa7ad1-f7d3-48f7-a3b7-a885d0200221.
Top 10 frames of crashing thread:
0 XUL mozilla::dom::WindowGlobalParent::Init dom/ipc/WindowGlobalParent.cpp
1 XUL mozilla::dom::BrowserParent::RecvNewWindowGlobal dom/ipc/BrowserParent.cpp:1329
2 XUL mozilla::dom::PBrowserParent::OnMessageReceived ipc/ipdl/PBrowserParent.cpp:6248
3 XUL mozilla::dom::PContentParent::OnMessageReceived ipc/ipdl/PContentParent.cpp:6544
4 XUL mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2215
5 XUL nsThread::ProcessNextEvent ipc/glue/MessageChannel.cpp:2007
6 XUL NS_ProcessPendingEvents xpcom/threads/nsThreadUtils.cpp:429
7 XUL nsBaseAppShell::NativeEventCallback widget/nsBaseAppShell.cpp:87
8 XUL nsAppShell::ProcessGeckoEvents widget/cocoa/nsAppShell.mm:440
9 CoreFoundation __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__
There are 47 crashes (from 26 installations) in nightly 75 starting with buildid 20200221095110. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1615403.
[1] https://hg.mozilla.org/mozilla-central/rev?node=be2f00ff66e6
Reporter | ||
Comment 1•5 years ago
|
||
For all these crashes the moz_crash_reason is always:
MOZ_DIAGNOSTIC_ASSERT(!mBrowsingContext->GetParent() || mBrowsingContext->GetEmbedderInnerWindowId()) (When creating a non-root WindowGlobalParent, the WindowGlobalParent for our embedder should've already been created.)
Comment 2•5 years ago
|
||
:calixte, since this bug is a regression, could you fill (if possible) the regressed_by field?
For more information, please visit auto_nag documentation.
Reporter | ||
Updated•5 years ago
|
Updated•5 years ago
|
Comment 3•5 years ago
|
||
I believe this is the same issue as bug 1617063, and should be fixed by the changes in that patch.
Updated•5 years ago
|
Description
•