| commit | aab443b709be482b746ffa47c3a04e69fade3e83 | |
| author | jdduke <jdduke@chromium.org> | |
| Tue, 9 Jun 2015 21:51:16 +0000 (9 14:51 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Tue, 9 Jun 2015 21:51:38 +0000 (9 21:51 +0000) | ||
| tree | 39e5489d98731c21651d5185bb1e8218035b13dc | treesnapshot (tar.gz zip) |
| parent | 44a4fb3ea1b344b993453f9b83f28d32b36b9d20 | commitdiff |
[Android] Use the UI thread for VSyncMonitorTest vsync requests
VSyncMonitor is not thread-safe, and is not intended to be. When a vsync
request is made from a non-UI thread, there is a race where both a
synthetic and frame-based callback can fire for the same request. Avoid
this by making sure VSyncMonitorTest only requests updates from the UI
thread, representative of production code behavior.
BUG=498007
Review URL: https://codereview.chromium.org/1166223003
Cr-Commit-Position: refs/heads/master@{#333580}
VSyncMonitor is not thread-safe, and is not intended to be. When a vsync
request is made from a non-UI thread, there is a race where both a
synthetic and frame-based callback can fire for the same request. Avoid
this by making sure VSyncMonitorTest only requests updates from the UI
thread, representative of production code behavior.
BUG=498007
Review URL: https://codereview.chromium.org/1166223003
Cr-Commit-Position: refs/heads/master@{#333580}