New issue
Advanced search Search tips

Issue 901455 link

Starred by 1 user
Status: Duplicate
Merged: issue 902072
Owner:
oysteine@google.com
Closed: Nov 27
Cc:
oysteine@google.com
dougman@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.2%-127.3% regression in media.desktop at 604472:604514

Project Member Reported by dougman@chromium.org, Nov 2 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 2 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=901455

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=114fea8ce9b74720df7ff7aea26045d49649034378e22037e1beb708678751ca


Bot(s) for this bug's original alert(s):

linux-perf

media.desktop - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 3

Cc: oysteine@google.com
Owner: oysteine@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12d1a2d5e40000

Perfetto: Fix for worker threads not finalizing proto packets by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/d420ce980291dbdee3d8a68594afbbfe5b75fbb4
cpu_time_percentage: 0.5697 → 0.7799 (+0.2102)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  None

Comment 4 by oysteine@google.com, Nov 27

Mergedinto: 902072
Status: Duplicate (was: Assigned)
►

Sign in to add a comment