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

Issue 886739 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
xidac...@chromium.org
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.7% regression in system_health.memory_mobile at 589876:589951

Project Member Reported by alexclarke@chromium.org, Sep 19 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 19 

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

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


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

Android Nexus5 Perf

system_health.memory_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 22

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

[Debugging] Don't DumpWithoutCrash in TouchActionFilter by xidachen@chromium.org
https://chromium.googlesource.com/chromium/src/+/6e232c819e454abaae731fdb596dcd078061cb63
5.244e+07 → 5.377e+07 (+1.326e+06)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

Comment 5 by xidac...@chromium.org, Oct 1

Owner: ----
Status: Untriaged (was: Assigned)
My CL removes some debugging instrumentation, it should not cause any memory regression.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Oct 2 

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14a9b18f640000

The swarming task expired. The bots are likely overloaded, dead, or misconfigured.
►

Sign in to add a comment