| commit | a4993aaf8edf91dd37db098aa19809f9cdecfec2 | |
| author | dyen <dyen@chromium.org> | |
| Fri, 13 Feb 2015 02:02:09 +0000 (12 18:02 -0800) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Fri, 13 Feb 2015 02:02:38 +0000 (13 02:02 +0000) | ||
| tree | 022917d04ed081f2197fb5c7e69e4468bddf68c5 | treesnapshot (tar.gz zip) |
| parent | 964602788cc2d0a2b0cb89fcbe1691852d25f251 | commitdiff |
Fix GPU Tracing offset calculation.
I found every once in awhile the offset on android would be wrong for a
trace, I tracked it down to occasionally between the time we calculate
the offset and begin the trace the GPU will reset the timing. Moving
the offset calculation until after we start the query fixes this
issue.
R=dcastagna@chromium.org, vmiura@chromium.org
BUG=None
TEST=local tracing 5 times and didn't see the offset calculation wrong.
Review URL: https://codereview.chromium.org/924533005
Cr-Commit-Position: refs/heads/master@{#316129}
I found every once in awhile the offset on android would be wrong for a
trace, I tracked it down to occasionally between the time we calculate
the offset and begin the trace the GPU will reset the timing. Moving
the offset calculation until after we start the query fixes this
issue.
R=dcastagna@chromium.org, vmiura@chromium.org
BUG=None
TEST=local tracing 5 times and didn't see the offset calculation wrong.
Review URL: https://codereview.chromium.org/924533005
Cr-Commit-Position: refs/heads/master@{#316129}
| gpu/command_buffer/service/gpu_timing.cc | diffblobblamehistory |