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

Issue 809457 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Mar 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

287.5% regression in system_health.memory_mobile at 533472:533605

Project Member Reported by kraynov@chromium.org, Feb 6 2018

Issue description

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

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


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

android-webview-nexus5X
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/169fd091840000
Some of the alerts recovered, but not all. Trying a bisect on a different metric.
Cc: roc...@chromium.org yfried...@chromium.org torne@chromium.org s...@chromium.org pasko@chromium.org agrieve@chromium.org
Owner: agrieve@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11dca57c440000

Move initCommandLine() to attachBaseContext (take 2) by agrieve@chromium.org
https://chromium.googlesource.com/chromium/src/+/7ee6c14b661b0abdfb91f8f0c8a07c34f1d353bc

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Not sure what to make of this. Very unlikely that this change affected memory usage. Especially not by 300%.

Comment 8 by pasko@chromium.org, Mar 7 2018

could it shift the time when the memory dump is made?
Status: WontFix (was: Assigned)
Looks like the memory graph recovered after a few runs:

https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICQjJHYoAkM

Sign in to add a comment