Issue metadata
Sign in to add a comment
|
H264 stats went to 0 for browser_tests at 392452:392460 |
||||||||||||||||||||
Issue descriptionSimilar to issue 611402 but with another blame range: https://chromium.googlesource.com/chromium/src/+log/c1300bcc9f5d724be1f08bf4d0ec3f3ca2cbe531%5E..520ed318ae5da996aebc47f09bb1a13c2c0a301f I also don't see what's going on here, could https://chromium.googlesource.com/chromium/src/+/f8ec6afcc3998e96bcaf0a7a7ac24c979b40a83f be causing this? That triggered issue 611392 .
,
May 12 2016
,
May 12 2016
This CL triggers HW encoder, and goog_avg_encode_ms is not working for any HW encoders. See https://bugs.chromium.org/p/chromium/issues/detail?id=597087 and https://bugs.chromium.org/p/chromium/issues/detail?id=350106 .
,
May 13 2016
,
May 14 2016
,
May 14 2016
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 10 2016
This issue has been moved once and is lower than Pri-1. Removing the milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 29 2016
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by kjellander@chromium.org
, May 12 2016