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

Issue 847495 link

Starred by 1 user
Status: Duplicate
Merged: issue 847448
Owner:
danakj@chromium.org
Closed: Jun 2018
Cc:
danakj@chromium.org
█ kraynov@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

43.9% regression in system_health.memory_mobile at 559517:559751

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

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

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

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


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

android-webview-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 1 2018

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

Remove GL context use from LayerTreeResourceProvider. by danakj@chromium.org
https://chromium.googlesource.com/chromium/src/+/5a196055274269b28b99be81b56faf3ef931f5b9
2.363e+06 → 3.4e+06 (+1.037e+06)

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

Comment 4 by danakj@chromium.org, Jun 1 2018

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

Sign in to add a comment