Closed Bug 1180860 Opened 9 years ago Closed 9 years ago

Ensure no APZ code interleaves use of the nsIThread message loop with the chromium MessageLoop

Categories

(Core :: Panning and Zooming, defect)

Product:
Core
Component:
Panning and Zooming
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: kats, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: arch, Whiteboard: [gfx-noted])

From bug 1169802 comment 7: > Oh. The touch-end event goes from the compositor thread -> root process main > thread via NS_DispatchToMainThread [1] whereas the state-change notification > goes from the compositor thread -> root process main thread via the chromium > message loop [2]. [2] is probably faster than [1], resulting in the > out-of-order arrival in the child process. Mixing use of the two different message loops can result in unexpected ordering of events, which we should avoid. Filing this bug to track this issue.
Whiteboard: [gfx-noted]
I believe the consolidation of the XPCOM and Chromium event loops in bug 1269056 makes this bug moot.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
See Also: → https://bugzilla.mozilla.org/show_bug.cgi?id=1269056
You need to log in before you can comment on or make changes to this bug.