New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 809445 link

Starred by 1 user
Status: Duplicate
Merged: issue 809446
Owner:
█ hpayer@chromium.org
Last visit > 30 days ago
Closed: Mar 2018
Cc:
mlippautz@chromium.org
█ hpayer@chromium.org
haraken@chromium.org
█ kraynov@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

35.9% regression in blink_perf.shadow_dom at 533607:533655

Project Member Reported by kraynov@chromium.org, Feb 6 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Feb 6 2018 

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

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


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

chromium-rel-mac11-air
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Feb 6 2018

Cc: haraken@chromium.org hpayer@chromium.org mlippautz@chromium.org
Owner: hpayer@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1283dd91840000

Oilpan: Remove Coalesce() logic. by hpayer@chromium.org
chromium @ fa293678b3eceaa1ed646ada4865bb875926aef6

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

Comment 4 by hpayer@chromium.org, Mar 23 2018

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

Sign in to add a comment