Closed
Bug 1158970
Opened 9 years ago
Closed 4 years ago
Compositor and controller threads can race when accessing Axis::mVelocity
Categories
(Core :: Panning and Zooming, defect, P3)
Core
Panning and Zooming
Tracking
()
RESOLVED
DUPLICATE
of bug 1642884
Tracking | Status | |
---|---|---|
firefox40 | --- | affected |
People
(Reporter: botond, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [gfx-noted])
Code in AsyncPanZoomController and Axis often accesses Axis::mVelocity without holding the APZC's mMonitor. This can lead to races between the compositor and controller threads. For example, the compositor thread could be updating the velocity while sampling an animation, while the controller thread is updating the velocity in response to an input event. We should avoid these races. One way to do so would be to make sure all accesses to Axis::mVelocity are protected by mMonitor, although this may be fairly tedious as there are a lot of such accesses.
Reporter | ||
Updated•9 years ago
|
Whiteboard: [gfx-noted]
Updated•6 years ago
|
Priority: -- → P3
Reporter | ||
Comment 1•4 years ago
|
||
This was fixed in bug 1642884.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•