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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-6HqtwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgu7fvvgsM


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

android-nexus5X

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

I think that is incremental wrapper tracing. The regression comes mainly from imgur. Not sure if we can do anything in the full gc case. I guess we have to pay the price there.

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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@432945  20.071   40.3406  50  good
chromium@432982  18.5637  30.3634  49  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 668976

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.browsing_mobile_ignition
Test Metric: v8-gc-full-mark-compactor_max/v8-gc-full-mark-compactor_max
Relative Change: None

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


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

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

Regression did not disappear when reverting the flag. Bouncing back.

Recovered.