Put together some .md MEDIA_LOG() best-practices in our code |
||||
Issue descriptione.g. discussion like https://chromium-review.googlesource.com/c/598702/3/media%252Ffilters%252Fdecoder_stream.cc#609 can become burdensome when repeated. ++documentation would help, especially as we begin to consider refining the media logging stuff (bug 752279, bug 737768, or perhaps things like adding some validation of messages to presubmit scripts). Credit to xhwang@ for suggesting this!
,
Oct 18
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Today
(21 hours ago)
Dale, moving to "Available" and over to you to confirm this is still something intended to do. Thanks.
,
Today
(19 hours ago)
=>wolenetz. We've made a lot of improvements to chrome://tracing, so most folks should just use that now. But we did just get a question on media-dev@ about how to debug MSE. So might be worth some investment. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Oct 18 2017