New issue
Advanced search Search tips

Issue 844602 link

Starred by 1 user
Status: WontFix
Owner:
chrishtr@chromium.org
Closed: May 2018
Cc:
npm@chromium.org
chrishtr@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

30.5%-49% regression in system_health.memory_desktop at 558262:558654

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

Comment 1 by 42576172...@developer.gserviceaccount.com, May 18 2018 

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

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


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

chromium-rel-win7-dual
chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 18 2018

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

Apply fixed-position scroll offset if the containing block is ancestor. by chrishtr@chromium.org
https://chromium.googlesource.com/chromium/src/+/edc066c316b24fb3dea226ae6c1c5c1fdee062c3

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

Comment 4 by chrishtr@chromium.org, May 19 2018

Status: WontFix (was: Assigned)
Back to normal
►

Sign in to add a comment