Crash in [@ mozilla::dom::Promise::MaybeSomething<T> | mozilla::dom::Promise::MaybeResolve | mozilla::dom::WorkerFetchResponseRunnable::WorkerRun]
Categories
(Core :: DOM: Workers, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox-esr115 | --- | unaffected |
firefox115 | --- | unaffected |
firefox116 | + | fixed |
firefox117 | --- | fixed |
People
(Reporter: aryx, Assigned: edenchuang)
References
Details
(Keywords: crash, regression)
Crash Data
5 crashes from 5 installations, all with Firefox 116.0b1 on Windows. The 4 reports who shared the url submitted localhost urls.
Crash report: https://crash-stats.mozilla.org/report/index/4e1bb849-66d7-40f6-9ecb-cd4b80230706
Reason: EXCEPTION_ACCESS_VIOLATION_READ
Top 10 frames of crashing thread:
0 xul.dll RefPtr<nsIGlobalObject>::get const mfbt/RefPtr.h:325
0 xul.dll RefPtr<nsIGlobalObject>::operator nsIGlobalObject* const mfbt/RefPtr.h:338
0 xul.dll mozilla::dom::Promise::MaybeSomething<RefPtr<mozilla::dom::Response>&> dom/promise/Promise.h:419
1 xul.dll mozilla::dom::Promise::MaybeResolve dom/promise/Promise.h:94
1 xul.dll mozilla::dom::WorkerFetchResponseRunnable::WorkerRun dom/fetch/Fetch.cpp:827
2 xul.dll mozilla::dom::WorkerRunnable::Run dom/workers/WorkerRunnable.cpp:372
3 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1193
3 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:480
4 xul.dll mozilla::dom::WorkerPrivate::DoRunLoop dom/workers/WorkerPrivate.cpp:3405
5 xul.dll mozilla::dom::workerinternals:: dom/workers/RuntimeService.cpp:2141
Updated•1 year ago
|
Updated•1 year ago
|
Comment 2•1 year ago
|
||
The bug is marked as tracked for firefox116 (beta). We have limited time to fix this, the soft freeze is in 13 days. However, the bug still isn't assigned.
:jstutte, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Reporter | ||
Updated•1 year ago
|
Assignee | ||
Comment 3•1 year ago
|
||
I take a look at it since I am resolving a similar issue.
Updated•1 year ago
|
Assignee | ||
Comment 4•1 year ago
|
||
I think this is a duplicate issue with bug 1837736. I submit a patch on bug 1837736. Let see if the patch helps on this bug or not.
Comment 5•1 year ago
|
||
appears fixed since build 20230719160709 in nightly. bug 1837736 has been uplifted to beta for 116.0b8. If there are no crashes there, I'll close this ticket as fixed
Updated•1 year ago
|
Updated•1 year ago
|
Description
•