[Fission] Crash in [@ mozilla::dom::PContentChild::SendCacheBrowsingContextChildren]
Categories
(Core :: DOM: Navigation, defect, P3)
Tracking
()
Fission Milestone | M5 |
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox72 | --- | wontfix |
firefox73 | --- | wontfix |
firefox74 | --- | wontfix |
firefox75 | --- | fixed |
People
(Reporter: jan, Assigned: nika)
References
(Regression, )
Details
(Keywords: crash, nightly-community, regression)
Crash Data
Attachments
(1 file)
(deleted),
image/jpeg
|
Details |
Came from Google and noticed crashed YouTube iframes. I couldn't reproduce it.
This bug is for crash report bp-995ca626-ad1d-417f-a2a7-3c82e0200208.
MOZ_RELEASE_ASSERT(!aParam->IsDiscarded()) (Cannot send discarded BrowsingContext between processes!)
Top 10 frames of crashing thread:
0 libxul.so mozilla::ipc::IPDLParamTraits<mozilla::dom::BrowsingContext*>::Write docshell/base/BrowsingContext.cpp:1521
1 libxul.so mozilla::dom::PContentChild::SendCacheBrowsingContextChildren ipc/ipdl/PContentChild.cpp:7477
2 libxul.so nsDocShell::SetupNewViewer docshell/base/nsDocShell.cpp:7989
3 libxul.so nsDocShell::Embed docshell/base/nsDocShell.cpp:5777
4 libxul.so nsDocShell::CreateContentViewer docshell/base/nsDocShell.cpp:7806
5 libxul.so nsDSURIContentListener::DoContent docshell/base/nsDSURIContentListener.cpp:168
6 libxul.so nsDocumentOpenInfo::TryContentListener uriloader/base/nsURILoader.cpp:632
7 libxul.so nsDocumentOpenInfo::DispatchContent uriloader/base/nsURILoader.cpp:313
8 libxul.so nsDocumentOpenInfo::OnStartRequest uriloader/base/nsURILoader.cpp:191
9 libxul.so mozilla::net::HttpChannelChild::DoOnStartRequest netwerk/protocol/http/HttpChannelChild.cpp:707
Comment 1•5 years ago
|
||
Can this happen even without Fission?
Looks like yes, based on crash-stat this is happening.
Updated•5 years ago
|
Comment 2•5 years ago
|
||
[Tracking Requested - why for this release]:
Crashes aren't nice.
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Comment 3•5 years ago
|
||
As Nika said, we hope to alleviate this with bug 1615403. Let's have another look at this bug after that lands.
Comment 4•5 years ago
|
||
Nika asked me to assign this bug to her because she is working on MaybeDiscarded bug 1615403.
Tracking for Fission dogfooding (M5) because this is a common Fission crash.
Updated•5 years ago
|
Comment 5•5 years ago
|
||
The priority flag is not set for this bug.
:kmag, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 6•5 years ago
|
||
Low level of crashes on beta and we are nearing the end of the beta cycle, marking as wontfix for 74.
Comment 7•5 years ago
|
||
P3 because crash volume is low. We are still tracking it for Fission dogfooding (M5).
While this crash is not Fission-specific, 29 of 30 crash reports from 75 Nightly had Fission enabled.
Assignee | ||
Comment 8•5 years ago
|
||
This should be fixed now that bug 1615403 has landed.
Updated•5 years ago
|
Description
•