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

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


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

android-nexus7v2

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

=== Auto-CCing suspected CL author avayvod@google.com ===

Hi avayvod@google.com, 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 : Anton Vayvod
  Commit : 09fa66e1baaa95d069bbd6620670311ae8aa4dc5
  Date   : Thu Jul 20 23:02:12 2017
  Subject: [RemotePlayback] Add media source info to the RemotePlayback availability url

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_news/load_news_irctc
  Change       : 0.87% | 23627082.8571 -> 23833452.0

Revision             Result                  N
chromium@488266      23627083 +- 123083      7       good
chromium@488408      23650684 +- 217184      6       good
chromium@488449      23604692 +- 241818      6       good
chromium@488464      23673458 +- 476883      14      good
chromium@488465      23819297 +- 135131      6       bad       <--
chromium@488466      23813316 +- 171225      6       bad
chromium@488468      23837401 +- 663786      21      bad
chromium@488472      23888426 +- 418390      14      bad
chromium@488479      23913735 +- 632704      9       bad
chromium@488550      23833452 +- 322907      9       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=load.news.irctc system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973191586971564304


For feedback, file a bug with component Speed>Bisection

 Issue 747896  has been merged into this issue.

 Issue 747899  has been merged into this issue.

 Issue 747903  has been merged into this issue.

 Issue 747905  has been merged into this issue.

 Issue 747892  has been merged into this issue.

 Issue 747906  has been merged into this issue.

 Issue 747908  has been merged into this issue.

 Issue 747893  has been merged into this issue.

 Issue 747894  has been merged into this issue.

 Issue 747891  has been merged into this issue.

 Issue 747895  has been merged into this issue.

 Issue 747902  has been merged into this issue.

 Issue 747904  has been merged into this issue.

 Issue 747876  has been merged into this issue.

Issue 748494 has been merged into this issue.

Issue 747940 has been merged into this issue.

Anton is there somebody you could hand this bug over to?

CCing some interested parties :)

I hoped the memory regression would be minimized after https://chromium-review.googlesource.com/c/chromium/src/+/584019

Would the bots confirm that or does someone need to verify?

I'm looking at a few graphs corresponding to bisects, and I'm not seeing an improvement at r492491. Examples:
https://chromeperf.appspot.com/group_report?sid=f61fe34c9e1d41b7e21538ed909a1494400afd55c6d3c2771ef0b06af1692f60
https://chromeperf.appspot.com/group_report?sid=3c735fdaf2108ca6986ae49dcd32365492e207dc16bcef115a6f0b3b49f17716
https://chromeperf.appspot.com/group_report?sid=65fbf91ea374c49435c733f55cd53d3486ad47c01bb25228b5a433f841452835

avayvod: ping on this. it's a pretty widespread memory regression. you can see the graphs linked in the first comment of the bug: https://chromeperf.appspot.com/group_report?bug_id=747890

mlamouri: Are you planning to look at this memory regression?

Sorry about this. I was assigned this following avayvod@'s departure. I could have a look but it would be deep into my todo-list.

Assigning to tguilbert@ so they can have a look as part of their Remote Playback refactor.