Closed Bug 1603215 Opened 4 years ago Closed 4 years ago

Crash in [@ mozilla::dom::ContentParent::RecvCacheBrowsingContextChildren]

Categories

(Core :: DOM: Navigation, defect, P2)

defect

Tracking

()

RESOLVED WORKSFORME
Fission Milestone M5

People

(Reporter: neha, Unassigned)

Details

(Keywords: crash, testcase-wanted)

Crash Data

This bug is for crash report bp-d3bb6194-d318-4ae9-a420-89edb0191211.

Top 10 frames of crashing thread:

0 XUL mozilla::dom::ContentParent::RecvCacheBrowsingContextChildren dom/ipc/ContentParent.cpp:5928
1 XUL mozilla::dom::PContentParent::OnMessageReceived ipc/ipdl/PContentParent.cpp:11654
2 XUL mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2209
3 XUL mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:2004
4 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1250
5 XUL NS_ProcessPendingEvents xpcom/threads/nsThreadUtils.cpp:434
6 XUL nsBaseAppShell::NativeEventCallback widget/nsBaseAppShell.cpp:87
7 XUL nsAppShell::ProcessGeckoEvents widget/cocoa/nsAppShell.mm:440
8 CoreFoundation __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ 
9 CoreFoundation __CFRunLoopDoSource0 

It happened (with Fission enabled) when I opened a new tab, entered a URL and it crashed right after the page loaded. Haven't been able to reproduce it.

Fission Milestone: --- → M5
Priority: -- → P2

WFM no crash reports since 73.0a1.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.