Open Bug 1761829 Opened 3 years ago Updated 1 years ago

Make FetchStreamReader::CloseAndRelease more clearly re-entrancy safe

Categories

(Core :: DOM: Networking, enhancement, P3)

Product:
Core
Component:
DOM: Networking
Type:
enhancement

Tracking

()

Tracking Flags:
Tracking Status
firefox-esr91 --- unaffected
firefox98 --- unaffected
firefox99 --- unaffected
firefox100 --- affected

People

(Reporter: mgaudet, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

+++ This bug was initially created as a clone of Bug #1760419 +++

FetchStreamReader::CloseAndRelease needs to handle re-entrancy in a more rigorous manner to avoid crashes like in Bug 1760419.

Perhaps cleanup should be re-scheduled as a separate task?

Set release status flags based on info from the regressing bug 1750298

status-firefox100: --- → affected
status-firefox98: --- → unaffected
status-firefox99: --- → unaffected
status-firefox-esr91: --- → unaffected

:evilpie, since you are the author of the regressor, bug 1750298, could you take a look?
For more information, please visit auto_nag documentation.

Flags: needinfo?(evilpies)
Flags: needinfo?(evilpies)
Blocks: 1750298
No longer regressed by: 1750298
Blocks: fetch
Severity: -- → N/A
Priority: -- → P3
Whiteboard: [necko-triaged]
You need to log in before you can comment on or make changes to this bug.