New issue
Advanced search Search tips

Issue 808663 link

Starred by 1 user
Status: Duplicate
Merged: issue 807331
Owner:
danakj@chromium.org
Closed: Feb 2018
Cc:
danakj@chromium.org
vmp...@chromium.org
npm@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1% regression in memory.desktop at 533368:533487

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

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

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

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


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

chromium-rel-win10
Project Member

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

Cc: danakj@chromium.org vmp...@chromium.org
Owner: danakj@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11b7048e840000

Fix memory dumps for ResourcePool. by danakj@chromium.org
chromium @ 1db4fe55034be340988580d95f52bc029146e539

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

Comment 4 by danakj@chromium.org, Feb 6 2018

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

Sign in to add a comment