Crash in [@ IPCError-browser | RecvCreateWindow New BrowsingContext has mismatched LoadContext]
Categories
(Core :: DOM: Navigation, defect, P2)
Tracking
()
Fission Milestone | M6 |
Tracking | Status | |
---|---|---|
firefox75 | --- | unaffected |
firefox76 | --- | unaffected |
firefox77 | --- | wontfix |
firefox78 | --- | fixed |
People
(Reporter: gsvelto, Assigned: nika)
References
Details
(Keywords: crash)
Crash Data
This bug is for crash report bp-58169edb-1ccd-45d4-b1d8-a96950200412.
Top 10 frames of crashing thread:
0 libxul.so bool js::jit::GetNativeDataPropertyPure<false> js/src/jit/VMFunctions.cpp:1611
1 @0x2cf1973f67fa
2 @0x2cf1973df0d2
3 @0x7f093b715547
4 @0x2cf1973ee3e0
5 @0x7f0945d2ba97
6 @0x2cf1973ee3e0
7 @0x7f094322180f
8 @0x2cf19739f48e
9 libxul.so js::jit::MaybeEnterJit js/src/jit/Jit.cpp:200
Looks like this started with bug 1616353.
Comment 1•4 years ago
|
||
Nika added this assertion recently. She'll add some new assertions to help diagnose this error.
The crash report in comment 0 has an unsigned extension installed and didn't have Fission enabled. Is this related to first-party isolation?
Tracking for Fission dogfooding milestone (M5), though this crash is affecting only non-Fission users for now.
P2 because the crash volume is still low: 34 crashes from 13 installations.
These are current, open bugs with a Severity of critical
. The Severity of these bugs is being changed to S2
to be consistent with the May 4 2020 Severity definitions.
Please let Release Management know if these bugs are still S2
.
Assignee | ||
Comment 3•4 years ago
|
||
I'm hopeful that this might be fixed by the changes in bug 1631332, so if the crash rate here for nightlies after that patch is merged drop to zero, I'm going to close out this bug.
Assignee | ||
Comment 4•4 years ago
|
||
Looks like the reports stopped after bug 1631332 landed, so marking as a dup.
Updated•4 years ago
|
Description
•