Closed Bug 1842017 Opened 1 year ago Closed 1 year ago

Crash in [@ mozilla::dom::Promise::MaybeSomething<T> | mozilla::dom::Promise::MaybeResolve | mozilla::dom::WorkerFetchResponseRunnable::WorkerRun]

Categories

(Core :: DOM: Workers, defect, P2)

defect

Tracking

()

RESOLVED FIXED
117 Branch
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

Any idea what started these?

Flags: needinfo?(jjalkanen)
Flags: needinfo?(jjalkanen) → needinfo?(bugmail)

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.

Flags: needinfo?(jstutte)
Crash Signature: [@ mozilla::dom::Promise::MaybeSomething<T> | mozilla::dom::Promise::MaybeResolve | mozilla::dom::WorkerFetchResponseRunnable::WorkerRun] → [@ mozilla::dom::Promise::MaybeSomething<T> | mozilla::dom::Promise::MaybeResolve | mozilla::dom::WorkerFetchResponseRunnable::WorkerRun] [@ mozilla::dom::Promise::MaybeSomething<T> | mozilla::dom::Promise::MaybeResolve<T> | mozilla::dom::WorkerFetchResp…

I take a look at it since I am resolving a similar issue.

Assignee: nobody → echuang
Flags: needinfo?(jstutte)
Flags: needinfo?(bugmail)
Severity: -- → S2
Priority: -- → P2

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.

Depends on: 1837736
See Also: → 1838246

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

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 117 Branch
You need to log in before you can comment on or make changes to this bug.