Crash in [@ mozilla::ipc::FatalError | mozilla::ipc::IProtocol::HandleFatalError | mozilla::ipc::IProtocol::FatalError | nsDocShellLoadState::nsDocShellLoadState]
Categories
(Core :: IPC, defect)
Tracking
()
People
(Reporter: vhilla, Assigned: vhilla)
References
Details
(Keywords: regression, Whiteboard: [tbird topcrash])
Crash Data
Attachments
(6 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr115+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr140+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr153+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-release+
|
Details | Review |
Crash report: https://crash-stats.mozilla.org/report/index/e3799b4d-4405-4f7c-ac7c-5dc1c0260713
This is coming from a different check than bug 2048851. That bug was regressed by bug 2045635, which is only in Nightly so far, it's fixed and the crash rate in nightly goes down. But we also see an increase in crashes on beta.
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Comment 1•2 months ago
|
||
The crashes on beta all go through ipc/ipdl/PBrowserBridgeParent.cpp:471, which is PBrowserBridge::Msg_LoadURL__ID. The three ESR ones are PNecko::Msg_PDocumentChannelConstructor__ID.
Updated•2 months ago
|
| Assignee | ||
Comment 3•2 months ago
|
||
I hope the crash volume won't increase too much. I don't know how these crashes occur, a reproducible example would be helpful. If the rate increases, we could early return in release builds before SendLoadURL to at least avoid content crashes. Maybe someone can have a look at protected data, i.e. what pages are crashing?
Updated•2 months ago
|
| Assignee | ||
Comment 4•1 month ago
|
||
Updated•1 month ago
|
| Assignee | ||
Comment 5•1 month ago
|
||
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/61403 for changes under testing/web-platform/tests
Comment 8•1 month ago
|
||
| bugherder | ||
Upstream PR merged by moz-wptsync-bot
Upstream PR merged
Comment 11•1 month ago
|
||
:vhilla did you want to uplift this to 154 beta? If so, please add uplift requests
| Assignee | ||
Comment 12•1 month ago
|
||
STR
- Go to
https://example.com - In the console, enter
document.body.append(Object.assign(document.createElement("iframe"), { src: "https://example.org" })); - In the console, enter
document.querySelector("iframe").src = "javascript:0;"
| Assignee | ||
Comment 13•1 month ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D312706
Updated•1 month ago
|
Comment 14•1 month ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined/Reason for urgency: parent-process crash
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: no
- Steps to reproduce for manual QE testing: See comment 12
- Risk associated with taking this patch: low
- Explanation of risk level: Reject cross origin javascript URIs through
iframe.srcin content, as we already do forwindow.openandlocation. The parent would reject these anyway. - String changes made/needed?: No
- Is Android affected?: yes
Comment 15•1 month ago
|
||
firefox-esr115 Uplift Approval Request
- User impact if declined/Reason for urgency: parent-process crash
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: no
- Steps to reproduce for manual QE testing: See comment 12
- Risk associated with taking this patch: low
- Explanation of risk level: Reject cross origin javascript URIs through
iframe.srcin content, as we already do forwindow.openandlocation. The parent would reject these anyway. - String changes made/needed?: No
- Is Android affected?: yes
| Assignee | ||
Comment 16•1 month ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D312706
| Assignee | ||
Comment 17•1 month ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D312706
Updated•1 month ago
|
Comment 18•1 month ago
|
||
firefox-esr140 Uplift Approval Request
- User impact if declined/Reason for urgency: parent-process crash
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: no
- Steps to reproduce for manual QE testing: See comment 12
- Risk associated with taking this patch: low
- Explanation of risk level: Reject cross origin javascript URIs through
iframe.srcin content, as we already do forwindow.openandlocation. The parent would reject these anyway. - String changes made/needed?: No
- Is Android affected?: yes
| Assignee | ||
Comment 19•1 month ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D312706
Updated•1 month ago
|
Comment 20•1 month ago
|
||
firefox-esr153 Uplift Approval Request
- User impact if declined/Reason for urgency: parent-process crash
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: no
- Steps to reproduce for manual QE testing: See comment 12
- Risk associated with taking this patch: low
- Explanation of risk level: Reject cross origin javascript URIs through
iframe.srcin content, as we already do forwindow.openandlocation. The parent would reject these anyway. - String changes made/needed?: No
- Is Android affected?: yes
| Assignee | ||
Comment 21•1 month ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D312706
Updated•1 month ago
|
Comment 22•1 month ago
|
||
firefox-release Uplift Approval Request
- User impact if declined/Reason for urgency: parent-process crash
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: no
- Steps to reproduce for manual QE testing: See comment 12
- Risk associated with taking this patch: low
- Explanation of risk level: Reject cross origin javascript URIs through
iframe.srcin content, as we already do forwindow.openandlocation. The parent would reject these anyway. - String changes made/needed?: No
- Is Android affected?: yes
| Assignee | ||
Comment 23•1 month ago
|
||
To clarify, html spec step 4 rejects cross origin javascript URIs, Chrome and Firefox do too. Web pages should not have a reason to trigger this bug, though a buggy page might do so and cause parent process crashes.
Updated•1 month ago
|
Updated•1 month ago
|
Comment 24•1 month ago
|
||
| uplift | ||
Updated•1 month ago
|
Updated•1 month ago
|
Comment 25•1 month ago
|
||
| uplift | ||
Updated•1 month ago
|
Updated•1 month ago
|
Comment 26•1 month ago
|
||
| uplift | ||
Comment 27•1 month ago
|
||
#2 crash for Thunderbird release 153.0 (non-ESR). All about opening PDFs
Updated•1 month ago
|
Updated•1 month ago
|
Comment 28•1 month ago
|
||
| uplift | ||
| Assignee | ||
Comment 29•1 month ago
•
|
||
The few Thunderbird failures I looked through are a different error. The sudden increase in frequency is surprising to me, I don't immediately see what change could've caused that.
nsDocShellLoadState URI changed while in content process
Do we have a bug that tracks the Thunderbird crashes? This bug is likely about something else and my change probably won't fix it.
Updated•1 month ago
|
Comment 30•1 month ago
|
||
| uplift | ||
Updated•1 month ago
|
Comment 31•1 month ago
|
||
(In reply to Vincent Hilla [:vhilla] from comment #29)
The few Thunderbird failures I looked through are a different error. The sudden increase in frequency is surprising to me, I don't immediately see what change could've caused that.
nsDocShellLoadState URI changed while in content process
Do we have a bug that tracks the Thunderbird crashes? This bug is likely about something else and my change probably won't fix it.
Filed bug 2057980
Updated•1 month ago
|
Updated•1 month ago
|
Description
•