New issue
Advanced search Search tips

Issue 834147 link

Starred by 1 user
Status: WontFix
Owner:
tfiga@chromium.org
Closed: May 2018
Cc:
posciak@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

video_VideoDecodeMemoryUsage.h264 regression

Project Member Reported by shenghao@chromium.org, Apr 18 2018 
CrOS 10304.0.0
caroline

https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICQtrXpvQkM

owenlin@ was the owner but he left the team. Assign to Pawel to triage.

Comment 1 by tfiga@chromium.org, May 10 2018

Status: WontFix (was: Assigned)
The jump observed was due to measuring method change. Note that the previous sample is

Value: 0.56394
Point ID: 32640001011700000
Time added: 2017-11-11T14:58:28.000Z
ChromeOS Version range: 64.10114.0.0 - 64.10117.0.0 
Chrome Version range: 64.0.3262.2 - 64.0.3264.0 

and actually the one marked as regression is

Value: 16.321
Point ID: 33190001030400000
Time added: 2018-01-16T04:19:05.000Z
ChromeOS Version range: 64.10117.0.0 - 65.10304.0.0 
Chrome Version range: 64.0.3264.0 - 65.0.3319.0 

Notice the date difference. The dates are respectively before and after the test was rewritten. In the meantime it was actually completely broken.

Comment 2 by tfiga@chromium.org, May 10 2018

Owner: tfiga@chromium.org
►

Sign in to add a comment