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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmuXB0AgM


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

android-webview-nexus6

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

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

Hi neis@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 : Georg Neis
  Commit : f846e7df71297bb700c7d77864b2a48ddb7634c1
  Date   : Tue May 16 11:14:05 2017
  Subject: [compiler] Make root detection thread-safe.

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/load_games/load_games_lazors
  Change       : 1.23% | 2253823.33333 -> 2281582.66667

Revision                           Result                  N
chromium@472324                    2253823 +- 15204.2      6      good
chromium@472344                    2256626 +- 102.879      6      good
chromium@472347                    2256597 +- 78.4687      6      good
chromium@472347,v8@1345de0b1e      2253919 +- 15204.2      6      good
chromium@472347,v8@f846e7df71      2281444 +- 125.984      6      bad       <--
chromium@472347,v8@1972e37392      2281439 +- 133.227      6      bad
chromium@472347,v8@04ac13deef      2281480 +- 159.097      6      bad
chromium@472347,v8@e92c52ba8a      2281465 +- 159.466      6      bad
chromium@472348                    2281561 +- 159.466      6      bad
chromium@472349                    2278751 +- 15225.9      6      bad
chromium@472354                    2281561 +- 159.466      6      bad
chromium@472364                    2281583 +- 171.829      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.games.lazors system_health.memory_mobile

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

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


| 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!

I'm a bit lost here. The "All graphs" link shows no graph at all, while the "Original alerts" link shows a graph in which I can't find a reference to this bug report.

This bug should have been marked a dupe of 724045, i think it may have been a glitch in the perf dashboard. Sorry about that.

I'm going to dupe this bug into that one, but not assign to you yet: your CL appears to have caused a 27KiB regression, but some other regressions on the bug are on the order of megabytes. Let's wait for the bisects to come back on those.