ImplCycleCollectionUnlink(std::shared_ptr<webgl::NotLostData>&) doesn't release the object
Categories
(Core :: Graphics: CanvasWebGL, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox-esr78 | --- | wontfix |
firefox78 | --- | wontfix |
firefox79 | --- | wontfix |
firefox80 | --- | fixed |
People
(Reporter: jgilbert, Assigned: jgilbert)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
This could cause not all memory to be released when the context is CC'd.
![]() |
Assignee | |
Updated•5 years ago
|
![]() |
Assignee | |
Comment 1•5 years ago
|
||
![]() |
Assignee | |
Updated•5 years ago
|
![]() |
Assignee | |
Comment 3•5 years ago
|
||
This seems like something we should uplift to Beta.
mccr8, what do you think? Would the pre-patch version leak like I fear?
Comment 4•5 years ago
|
||
(In reply to Jeff Gilbert [:jgilbert] from comment #3)
This seems like something we should uplift to Beta.
mccr8, what do you think? Would the pre-patch version leak like I fear?
Sure, it would be good to uplift. A missing unlink won't necessarily result in a leak. If you have a cycle, you just have to break one link in the chain for it to all fall apart, so it depends on precisely what sort of cycles this reference is involved in.
![]() |
||
Comment 5•5 years ago
|
||
bugherder |
Comment 6•5 years ago
|
||
Too late to uplift this to Fx79 at this point given that we're already in RC week, but I'd still consider taking this on ESR78 next cycle.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 7•5 years ago
|
||
Hi Jeff, does this need an ESR78 approval request?
![]() |
Assignee | |
Comment 8•5 years ago
|
||
I don't think it's important enough, and it's supposed to not be necessary, I now think. (CC code is inscrutable though)
If we do take it, there's another fix needed, or this can cause UAFs by itself.
Description
•