New issue
Advanced search Search tips

Issue 808632 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Feb 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.1%-138.9% regression in system_health.memory_mobile at 532471:532679

Project Member Reported by npm@chromium.org, Feb 2 2018

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=808632

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


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

android-nexus5
android-nexus5X
android-one
android-webview-nexus5X
android-webview-nexus6
chromium-rel-mac12
chromium-rel-win10
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/1181e9ae840000

Move ownership of software ResourcePool backings into the pool. by danakj@chromium.org
chromium @ 694134e2b295464c965306b2865250cd97173de2

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Mergedinto: 808666
Status: Duplicate (was: Assigned)

Sign in to add a comment