Closed Bug 1634596 Opened 4 years ago Closed 4 years ago

Crash in [@ IPCError-content | RecvConstructBrowser Null or discarded initial BrowsingContext]

Categories

(Core :: DOM: Content Processes, defect, P2)

Unspecified
Windows 10
defect

Tracking

()

RESOLVED FIXED
mozilla78
Fission Milestone M5b
Tracking Status
firefox-esr68 --- disabled
firefox75 --- disabled
firefox76 --- disabled
firefox77 --- disabled
firefox78 --- fixed

People

(Reporter: mccr8, Assigned: nika)

References

Details

(Keywords: crash, regression)

Crash Data

Attachments

(1 file)

This bug is for crash report bp-4a257f1c-25b3-47d8-9766-a85810200430.

Top 10 frames of crashing thread:

0 xul.dll mozilla::dom::ContentChild::ProcessingError dom/ipc/ContentChild.cpp:2230
1 xul.dll static mozilla::ipc::IPCResult::Fail ipc/glue/ProtocolUtils.cpp:58
2 xul.dll mozilla::dom::ContentChild::RecvConstructBrowser dom/ipc/ContentChild.cpp:1756
3 xul.dll mozilla::dom::PContentChild::OnMessageReceived ipc/ipdl/PContentChild.cpp:8517
4 xul.dll mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2110
5 xul.dll mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:1989
6 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1200
7 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:481
8 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:87
9 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:308

It looks like this first showed up in the 20200425094923 build. These are the changesets added in that build: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=db2e1d780268ab0a7dca1ea1ca81febcb33e926e&tochange=d8a8178627c4fab05f1eb46ee40f55db207c7c18

Bug 1580565 is in the range. Bug 1632098 is also kind of Fission-y.

It is still showing up in the April 29th builds.

Nika, do you think this might be a regression from bug 1580565? And might it be fixed by one of the other regression fixes you landed recently? Thanks.

It looks like this crash is Fission-only.

Flags: needinfo?(nika)
Component: DOM: Navigation → DOM: Content Processes

(It looks like bug 1632098 got backed out and didn't make it to a Nightly.)

This looks like it might be the same as the new crash signature :mattwoodrow noticed in bug 1618156 comment 12.

I think this is a regression from bug 1580565, caused in some of the similar situations as the crash which was fixed unfortunately. I think I know how it happens, but I haven't had the time to fix it properly.

Self-assigning this so I fix it soon.

Assignee: nobody → nika
Fission Milestone: --- → M5b
Flags: needinfo?(nika)
Priority: -- → P2

This is a temporary workaround for the crashes this can cause. A more thorough
fix to discarded ancestor issues will be implemented in bug 1634759.

Crash Signature: [@ IPCError-content | RecvConstructBrowser Null or discarded initial BrowsingContext] → [@ IPCError-content | RecvConstructBrowser Null or discarded initial BrowsingContext] [@ mozilla::dom::ContentChild::ProcessingError(mozilla::ipc::HasResultCodes::Result, char const*)]
Pushed by nlayzell@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/67c5870aef72
Avoid switching into a new process if an ancestor is discarded, r=farre
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla78
Blocks: 1618156
See Also: 1618156
See Also: → 1722378
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: