|
|
Created:
6 years, 8 months ago by jdduke (slow) Modified:
6 years, 7 months ago CC:
chromium-reviews, cc-bugs_chromium.org Base URL:
https://chromium.googlesource.com/chromium/src.git@master Visibility:
Public. |
DescriptionTrace the lifetime of CopyOutputRequest
The async readback case can be hard to follow with existing traces. Add an async
lifetime trace for each valid CopyOutputRequest, making clear both the lifetime
and frequency of such requests.
BUG=321624
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=266688
Patch Set 1 #
Total comments: 1
Patch Set 2 : Cleanup #Patch Set 3 : Fix #Messages
Total messages: 27 (0 generated)
skyostil@: Would this be at all useful? We don't seem to have much in the way of async readback trace coverage (or maybe I'm just not seeing it?).
https://codereview.chromium.org/239183003/diff/1/cc/output/copy_output_reques... File cc/output/copy_output_request.cc (right): https://codereview.chromium.org/239183003/diff/1/cc/output/copy_output_reques... cc/output/copy_output_request.cc:46: TRACE_EVENT_ASYNC_END0("cc", "CopyOutputRequest", this); Oops, forgot to delete this line.
In theory you can reconstruct this from the surrounding events, but since I'm lazy at heart I'm all for doing this -- especially since you want expensive operations like this to stand out. lgtm!
On 2014/04/25 20:20:53, Sami wrote: > In theory you can reconstruct this from the surrounding events, but since I'm > lazy at heart I'm all for doing this -- especially since you want expensive > operations like this to stand out. lgtm! Yeah, I considered hooking in at different points, but it involved extra bookkeeping to make sure we got the proper async termination. Thanks for review!
The CQ bit was checked by jdduke@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/jdduke@chromium.org/239183003/20001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: tryserver.chromium on linux_chromium_clang_dbg
The CQ bit was checked by danakj@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/jdduke@chromium.org/239183003/20001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: tryserver.chromium on linux_chromium_rel
The CQ bit was checked by jdduke@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/jdduke@chromium.org/239183003/40001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: tryserver.chromium on linux_chromium_chromeos_rel
The CQ bit was checked by jdduke@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/jdduke@chromium.org/239183003/40001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: tryserver.chromium on chromium_presubmit
The CQ bit was checked by jdduke@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/jdduke@chromium.org/239183003/40001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: tryserver.chromium on android_dbg_triggered_tests
The CQ bit was checked by jdduke@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/jdduke@chromium.org/239183003/40001
Message was sent while issue was closed.
Change committed as 266688 |