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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7szcswsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7pi4-AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7uW14ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrtGAyQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzp-IhQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgruOI7AgM


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

android-one
android-webview-nexus6

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975542244303510496

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975541946854285440

=== Auto-CCing suspected CL author ssid@chromium.org ===

Hi ssid@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Siddhartha
  Commit : 12fd478c980c2af7ea532d7470a350acc19c3a9d
  Date   : Mon Jun 26 20:23:24 2017
  Subject: Clear GL context when Chrome goes to background on low end devices

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/background_media/background_media_imgur

Revision             Result              N
chromium@482283      0.0 +- 0.0          6      good
chromium@482354      0.0 +- 0.0          6      good
chromium@482372      0.0 +- 0.0          6      good
chromium@482375      0.0 +- 0.0          6      good
chromium@482376      0.0 +- 0.0          6      good
chromium@482377      2228224 +- 0.0      6      bad       <--
chromium@482381      2228224 +- 0.0      6      bad
chromium@482389      2228224 +- 0.0      6      bad
chromium@482424      2228224 +- 0.0      6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=background.media.imgur system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8975542244303510496

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6128681266708480


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Issue 737329 has been merged into this issue.

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Siddhartha
  Commit : 12fd478c980c2af7ea532d7470a350acc19c3a9d
  Date   : Mon Jun 26 20:23:24 2017
  Subject: Clear GL context when Chrome goes to background on low end devices

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/background_media/background_media_imgur

Revision             Result              N
chromium@482283      0.0 +- 0.0          6      good
chromium@482354      0.0 +- 0.0          6      good
chromium@482372      0.0 +- 0.0          6      good
chromium@482375      0.0 +- 0.0          6      good
chromium@482376      0.0 +- 0.0          6      good
chromium@482377      2228224 +- 0.0      6      bad       <--
chromium@482381      2228224 +- 0.0      6      bad
chromium@482389      2228224 +- 0.0      6      bad
chromium@482424      2228224 +- 0.0      6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=background.media.imgur system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8975541946854285440

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6052811072077824


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Explictly assigning. A CL you landed tripped one of the speed metrics we measure in the lab. If this is the first time this has happened to one of your CLs, or if it's been a while, please read: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/addressing_performance_regressions.md

We're looking for one of the following:
1. Justification via explanation
2. Plan to revert or fix
3. Angry rage throwing of equipment at my head

Just be aware that I'm trained in trumpet playing and First Aid and am not afraid to use it.

Note: This was a bulk edit message and not very personal.

ssid: is this expected?

No response on the bug, not much we can do at this point.