Open
Bug 1242442
Opened 9 years ago
Updated 2 years ago
CompositorChild can be deleted from one of its own methods
Categories
(Core :: Graphics: Layers, defect, P3)
Core
Graphics: Layers
Tracking
()
NEW
People
(Reporter: nical, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [gfx-noted])
Not sure if it is a problem, but it's the kind of situation that we tend to assume never happens and can easily become a problem: TextureChild holds a strong reference to CompositorChild. This means that when receiving PTexture::__delete__, CompositorChild may destroy the last texture and get deleted in the process, in the middle of its message handling code. I've just run into this while trying to debug something else.
|
Reporter | |
Updated•9 years ago
|
Whiteboard: [gfx-noted]
|
|
Reporter | |
Comment 1•9 years ago
|
||
This will get fixed by one of the patches in bug 1215265.
Assignee: nobody → nical.bugzilla
Depends on: 1215265
|
|
Reporter | |
Comment 2•9 years ago
|
||
(In reply to Nicolas Silva [:nical] from comment #1)
> This will get fixed by one of the patches in bug 1215265.
Not so sure bug 1215265 fixed this actually. I haven't run into this since I opened the bug, though.
Assignee: nical.bugzilla → nobody
|
||
Updated•7 years ago
|
Priority: -- → P3
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•