New issue
Advanced search Search tips

Issue 792891 link

Starred by 1 user
Status: Duplicate
Merged: issue 782220
Owner:
drott@chromium.org
Closed: Dec 2017
Cc:
kojii@chromium.org
petermarshall@chromium.org
drott@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

17.6%-601% regression in v8.browsing_desktop at 521659:521790

Project Member Reported by petermarshall@chromium.org, Dec 7 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 7 2017 

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

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


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

chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-nvidia
chromium-rel-win8-dual
linux-release
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 7 2017

Cc: drott@chromium.org kojii@chromium.org
Owner: drott@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14f5c974040000

Roll HarfBuzz to 1.7.2
By drott@chromium.org · Tue Dec 05 14:44:55 2017
chromium @ 66aaf201efada2d0a2d1f3c090ef4858dd41c392

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

Comment 4 by drott@chromium.org, Dec 8 2017

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

Sign in to add a comment