Issue metadata
Sign in to add a comment
|
1.9%-67.7% regression in webrtc_perf_tests at 15009:15011 |
||||||||||||||||||||
Issue descriptionThis seems to be an improvement of VP9. The blame list is https://chromium.googlesource.com/external/webrtc/+log/51e9608f0194af090c83d9a3dd9efb43a39f8e6f..5de52fd38e8d80250d6e8ed79764ded1f39d4b5d, which contains a Chrome roll (https://chromium.googlesource.com/external/webrtc/+/37e4ad598d209fcec8abd677769e120b442007da). The Chrome roll in turn contains a libvpx roll with 90 commits.
,
Nov 16 2016
mflodman@: Please assign to someone who can confirm that these are good and expected improvements.
,
Nov 18 2016
,
Apr 25 2017
Since there is an owner, this bug is not untriaged. Updating the status.
,
May 6 2017
This regression has been included in a stable release and that stable channel is now deprecated. I'm closing this so that we won't have unresponsive performance regressions in the future. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by hlundin@chromium.org
, Nov 16 2016