[Video Capture] Add trace events to facilitate future bug investigation |
||
Issue descriptionFor a lot of bug investigations in the context of video capture, we have to use custom builds in order to enable the low-level event logs that allow us to see enough detail on what is going on. This is inefficient because it requires * The issue being reproducable on one of our own machines * Building and deploying a custom build of Chromium It would be nice if we could add trace events verbose enough to give us sufficient information to diagnose most issues. Trace events are relatively inexpensive and they do not require deploying custom builds to be collected. if provided with instructions on how to collect traces, these can often be provided by users. A good place to start would be to generate trace events for each log that we send to https://cs.chromium.org/chromium/src/content/browser/renderer_host/media/video_capture_manager.h?g=0&l=290.
,
Oct 8
Please feel free to go ahead. I'll assign myself as the owner, since only @chromium accounts can be assigned.
,
Oct 13
I confirmed late. Sorry. I'll try!
,
Oct 21
chfremer@ I am really sorry to have been late. I do not seem to understand the requirements properly. Could you give me a hint to proceed?
,
Jan 10
Sorry for the delayed response. I was out on paternity leave until the new year. As part of investigating some performance issue with taking photos on Android I ended up adding some trace events in various places, and since it seems useful to keep them I put them in this CL: https://chromium-review.googlesource.com/c/chromium/src/+/1405541 spzape@: If you are still interested, you are welcome to continue adding more events. The key work here is to figure out where strategically useful places are to add trace events so that we can get maximum use out of them without ending up adding one to every single method.
,
Jan 17
(6 days ago)
chfremer@: I'm sorry, I think it's going to be difficult now. |
||
►
Sign in to add a comment |
||
Comment 1 by sapz...@gmail.com
, Oct 6