Open
Bug 1870784
Opened 10 months ago
Updated 10 months ago
Take a look at nsAStreamCopier's lifecycle
Categories
(Core :: DOM: File, task, P3)
Core
DOM: File
Tracking
()
NEW
People
(Reporter: jstutte, Unassigned)
References
Details
From the discussion on D196765 and the pernosco session on bug 1870423 we might want to take a second (third?) look at:
- how
nsAStreamCopier
can ensure to be always released on its owning thread or - if we can reduce the impact of subsequent leaks caused by holding so many strong references
Reporter | ||
Updated•10 months ago
|
Reporter | ||
Updated•10 months ago
|
Severity: -- → S4
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•