New issue
Advanced search Search tips

Issue 847164 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 29
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.2%-8.2% regression in system_health.memory_desktop at 561182:561445

Project Member Reported by petermarshall@chromium.org, May 28 2018

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

chromium-rel-win10
chromium-rel-win7-gpu-nvidia
win-high-dpi
Project Member

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

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

Flag flip for PageLifecycle. by panicker@chromium.org
https://chromium.googlesource.com/chromium/src/+/0ff4bba09cb7f17e709fe596c7819b205ba300f1

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Components: Speed>Metrics>SystemHealthRegressions
Components: -Speed>Metrics>SystemHealthRegressions
Owner: ----
Status: Available (was: Assigned)
Sorry for missing this bug!
Not sure how this CL could have any impact on desktop memory, as the feature (firing the page lifecycle callback) was not even enabled on desktop and was behind another flag on mobile.
So I believe this is the wrong culprit.
Status: WontFix (was: Available)
I think we can close this out given the graph has recovered.

Sign in to add a comment