New issue
Advanced search Search tips

Issue 824385 link

Starred by 1 user
Status: Duplicate
Merged: issue 825107
Owner:
danakj@chromium.org
Closed: Mar 2018
Cc:
danakj@chromium.org
chiniforooshan@chromium.org
kylec...@chromium.org
sky@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

9.6%-70.1% regression in system_health.memory_mobile at 544429:544577

Project Member Reported by chiniforooshan@chromium.org, Mar 21 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Mar 21 2018 

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

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


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

android-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 26 2018

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

Allocate shared memory/textures directly for UIResources. by danakj@chromium.org
https://chromium.googlesource.com/chromium/src/+/f77a89225113b8f47f36670265fb9130502170ca

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

Comment 4 by chiniforooshan@chromium.org, Mar 26 2018

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

Sign in to add a comment