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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZy2QELEhNTdG9wcGFnZUFsZXJ0UGFyZW50IqoBQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM1WC9zeXN0ZW1faGVhbHRoLm1lbW9yeV9tb2JpbGUvbWVtb3J5OmNocm9tZTphbGxfcHJvY2Vzc2VzOnJlcG9ydGVkX2J5X2Nocm9tZTpncHVtZW1vcnlidWZmZXI6ZWZmZWN0aXZlX3NpemVfYXZnL2xvYWRfc29jaWFsL2xvYWRfc29jaWFsX3R3aXR0ZXIMCxINU3RvcHBhZ2VBbGVydBix4xgM,agxzfmNocm9tZXBlcmZy2AELEhNTdG9wcGFnZUFsZXJ0UGFyZW50IqkBQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM1WC9zeXN0ZW1faGVhbHRoLm1lbW9yeV9tb2JpbGUvbWVtb3J5OmNocm9tZTphbGxfcHJvY2Vzc2VzOnJlcG9ydGVkX2J5X2Nocm9tZTpncHVtZW1vcnlidWZmZXI6ZWZmZWN0aXZlX3NpemVfYXZnL2xvYWRfc2VhcmNoL2xvYWRfc2VhcmNoX3Rhb2JhbwwLEg1TdG9wcGFnZUFsZXJ0GLHjGAw,agxzfmNocm9tZXBlcmZy2AELEhNTdG9wcGFnZUFsZXJ0UGFyZW50IqkBQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM1WC9zeXN0ZW1faGVhbHRoLm1lbW9yeV9tb2JpbGUvbWVtb3J5OmNocm9tZTphbGxfcHJvY2Vzc2VzOnJlcG9ydGVkX2J5X2Nocm9tZTpncHVtZW1vcnlidWZmZXI6ZWZmZWN0aXZlX3NpemVfYXZnL2xvYWRfZ2FtZXMvbG9hZF9nYW1lc19zcHljaGFzZQwLEg1TdG9wcGFnZUFsZXJ0GLHjGAw


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

android-nexus5X

https://chromeperf.appspot.com/report?sid=b394b23af152b8dfef46ccc4376fd2110a20944f3b82ab2a4de630baa4aa6267&rev=405937 shows that the value disappeared in the range r405938-r406392 (http://test-results.appspot.com/revision_range?start=405938&end=406392). I'll try to run a bisect.

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@405937  0.0   0.0      5  good

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 635520

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_search-memory:chrome:all_processes:reported_by_chrome:gpumemorybuffer:effective_size_avg/load_search_taobao
Relative Change: None
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/464
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004890960713429056


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5848515398336512

| 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 Tests>AutoBisect.  Thank you!

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@405937  0.0   0.0      5  good

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 635520

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_search-memory:chrome:all_processes:reported_by_chrome:gpumemorybuffer:effective_size_avg/load_search_taobao
Relative Change: None
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/464
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004890960713429056


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5848515398336512

| 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 Tests>AutoBisect.  Thank you!

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/474
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/474
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

We know that the r405937 is good (from #6) and r406089 is bad (from #8) now.

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@405987  0.0   0.0      5  good

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 635520

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_search-memory:chrome:all_processes:reported_by_chrome:gpumemorybuffer:effective_size_avg/load_search_taobao
Relative Change: None
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/502
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004628639022113328


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5820569589645312

| 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 Tests>AutoBisect.  Thank you!

Assuming no flakes, we can infer from #13 that the value disappeared between r405987 (good) and r406038 (bad).

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

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@405987  0.0   0.0      5  good

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 635520

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_search-memory:chrome:all_processes:reported_by_chrome:gpumemorybuffer:effective_size_avg/load_search_taobao
Relative Change: None
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/502
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004628639022113328


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5820569589645312

| 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 Tests>AutoBisect.  Thank you!

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/503
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/503
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

We can infer that the value disappeared between r405987 (good, #13) and r406004 (bad, #20): http://test-results.appspot.com/revision_range?start=405988&end=406004

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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N   Good?
chromium@405992  0.0   0.0      12  good
chromium@405998  0.0   0.0      8   bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 635520

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_search-memory:chrome:all_processes:reported_by_chrome:gpumemorybuffer:effective_size_avg/load_search_taobao
Relative Change: 0.00%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/510
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004525999379824768


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5796827413086208

| 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 Tests>AutoBisect.  Thank you!

Almost there: r405998 (good, #23) and r406004 (bad, #20).

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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N   Good?
chromium@406000  0.0   0.0      12  good
chromium@406002  0.0   0.0      8   bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 635520

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_search-memory:chrome:all_processes:reported_by_chrome:gpumemorybuffer:effective_size_avg/load_search_taobao
Relative Change: 0.00%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/512
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004272676475181392


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5830772200570880

| 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 Tests>AutoBisect.  Thank you!

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

One more bisect to go: r406002 (good, #26) and r406004 (bad, #20).

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@406003  0.0   0.0      5  good

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 635520

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_search-memory:chrome:all_processes:reported_by_chrome:gpumemorybuffer:effective_size_avg/load_search_taobao
Relative Change: None
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/513
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004255684649852864


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5328188817801216

| 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 Tests>AutoBisect.  Thank you!

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@406003  0.0   0.0      5  good

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 635520

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_search-memory:chrome:all_processes:reported_by_chrome:gpumemorybuffer:effective_size_avg/load_search_taobao
Relative Change: None
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/513
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004255684649852864


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5328188817801216

| 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 Tests>AutoBisect.  Thank you!

vmiura: It appears that your patch (r402702) relanded by picksi@ (r406004) resulted in data stoppage of the memory:chrome:all_processes:reported_by_chrome:gpumemorybuffer:effective_size_avg value (which is calculated from values reported from https://cs.chromium.org/chromium/src/content/browser/gpu/browser_gpu_memory_buffer_manager.cc?l=333. Can you please confirm whether this is correct behavior, or a bug?

Sorry for missing this.  It is expected - we don't use GPU Memory Buffers on Android when using GPU Raster, which my change enabled.

This test no longer has data.  Can we WontFix this?