Full browser crash by running new WebTransport(location.href) on MDN and google.com
Categories
(Core :: DOM: Networking, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox125 | --- | wontfix |
| firefox126 | --- | wontfix |
| firefox127 | --- | verified |
| firefox128 | --- | verified |
People
(Reporter: saschanaz, Assigned: kershaw)
References
Details
(Keywords: regression, Whiteboard: [necko-triaged] [necko-priority-queue])
Crash Data
Attachments
(1 file)
- Open https://developer.mozilla.org/
- Run
new WebTransport(location.href)on the devtools console
Expected: No crash
Actual: boom!
Crash report: https://crash-stats.mozilla.org/report/index/2325f8ed-6650-4638-a16b-b7bf10240507
Comment 1•2 years ago
|
||
Tried on two different pages (google.com and some mdn page) and got 2 different crash signatures:
https://crash-stats.mozilla.org/report/index/5245dfe5-6e6f-4b8a-a933-51fd30240507
https://crash-stats.mozilla.org/report/index/7fc7104d-5fda-4f13-94cf-d68960240507
Updated•2 years ago
|
Comment 2•2 years ago
|
||
Bisection:
Bug 1874464 - Turn on native HTTPS-RR DNS resolver on Nightly r=necko-reviewers,kershaw
Differential Revision: https://phabricator.services.mozilla.com/D198437
Comment 3•2 years ago
|
||
With network.dns.native_https_query = true , I get hte following regression range:
Bug 1852900 - Use android_res_nquery from libandroid.so to resolve HTTPS records on Android (API level >= 29) r=necko-reviewers,jesup
Depends on D194515
Differential Revision: https://phabricator.services.mozilla.com/D196068
Comment 4•2 years ago
|
||
Set release status flags based on info from the regressing bug 1874464
:valentin, since you are the author of the regressor, bug 1852900, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 5•2 years ago
|
||
This is not regressed by bug 1852900.
It's just that the HTTPS record can trigger this crash.
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 6•2 years ago
|
||
Comment 8•2 years ago
|
||
| bugherder | ||
Comment 9•2 years ago
|
||
The patch landed in nightly and beta is affected.
:kershaw, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox126towontfix.
For more information, please visit BugBot documentation.
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
I managed to reproduce the crash on a 2024-05-07 Nightly build on Windows 10, using the STR from Comment 0.
Verified as fixed on Firefox Nightly 128.0a1 and Firefox 127.0b4 on Windows 10, macOS 12, Ubuntu 22.
Description
•