Closed Bug 1820408 Opened 2 years ago Closed 2 years ago

Wrong-thread crash handling a close message

Categories

(Core :: Networking, defect, P2)

defect

Tracking

()

RESOLVED FIXED
112 Branch
Tracking Status
firefox112 --- fixed

People

(Reporter: jesup, Assigned: kershaw)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

https://treeherder.mozilla.org/logviewer?job_id=407889293&repo=try&lineNumber=7126

Crash due to wrong-thread assertion in WebTransportSessionProxy::CloseSession(), called on Socket Thread.

Looks to be intermittent

Flags: needinfo?(kershaw)

This happens because that RetargetTo is called too late.
I assume this can be easily fixed by calling RetargetTo earlier than resolving mResolver.

Assignee: nobody → kershaw
Severity: -- → S4
Flags: needinfo?(kershaw)
Priority: -- → P2
Whiteboard: [necko-triaged]
Pushed by kjang@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e738bc9b389d Call WebTransportSessionProxy::RetargetTo earlier, r=jesup,necko-reviewers
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: