Open
Bug 988858
(apz-threadsafe)
Opened 11 years ago
Updated 3 years ago
[meta] Ensure all of the APZ code is threadsafe
Categories
(Core :: Panning and Zooming, defect, P3)
Core
Panning and Zooming
Tracking
()
NEW
People
(Reporter: kats, Unassigned)
References
(Depends on 2 open bugs)
Details
(Keywords: correctness, meta, Whiteboard: gfx-noted)
We need to make sure that all the APZC code is threadsafe and has documented the threading assumptions. In particular this will be needed before we can either enable APZC on Fennec (where the input thread is different from the gecko thread) or tackle bug 930939.
Reporter | ||
Updated•11 years ago
|
Alias: apz-threadsafe
Reporter | ||
Comment 1•10 years ago
|
||
Seeing as how we already landed bug 930939 I don't think this is really "needed" before we can do APZ on Fennec. Removing dependencies, but leaving this bug around as there are probably some thready safety things we need to do in APZ code.
No longer blocks: apz-fennec, input-thread
Reporter | ||
Updated•9 years ago
|
Keywords: correctness
Whiteboard: gfx-noted
Reporter | ||
Updated•9 years ago
|
OS: Gonk (Firefox OS) → All
Updated•8 years ago
|
Priority: -- → P3
Comment 2•5 years ago
|
||
It seems like :decoder has found a systematic approach to discovering thread safety issues in APZ (and other) code via TSan. Thank you :)
Updated•5 years ago
|
Summary: [meta] Ensure all of the APZC code is threadsafe → [meta] Ensure all of the APZ code is threadsafe
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•