Closed
Bug 1746898
Opened 4 years ago
Closed 4 years ago
DOM XHR doesn't lock when generating a memory report
Categories
(Core :: DOM: Networking, defect)
Core
DOM: Networking
Tracking
()
RESOLVED
FIXED
97 Branch
People
(Reporter: jesup, Assigned: jesup)
References
(Blocks 1 open bug)
Details
(Keywords: csectype-race, sec-low, sec-other, Whiteboard: [post-critsmash-triage][adv-main97+r])
Attachments
(1 file)
DOM XHR doesn't take a lock when running memory reporting, though it accesses fields that need locks.
|
Assignee | |
Comment 1•4 years ago
|
||
|
||
Updated•4 years ago
|
Assignee: nobody → rjesup
Status: NEW → ASSIGNED
|
||
Comment 2•4 years ago
|
||
Lock around memory reporting for XHR r=smaug
https://hg.mozilla.org/integration/autoland/rev/998695a5708718e1d280c57be56c26acabdc7d74
https://hg.mozilla.org/mozilla-central/rev/998695a57087
Group: core-security → core-security-release
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox97:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 97 Branch
|
||
Updated•4 years ago
|
|
||
Updated•4 years ago
|
Flags: qe-verify-
Whiteboard: [post-critsmash-triage]
|
||
Updated•3 years ago
|
Whiteboard: [post-critsmash-triage] → [post-critsmash-triage][adv-main97+r]
|
||
Updated•3 years ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•