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

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


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

chromium-rel-mac11

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


===== SUSPECTED CL(s) =====
Subject : Reland of Add logic to ResourceProvider to correctly lock GpuMemoryBuffer Resources. (patchset #1 id:1 of https://codereview.chromium.org/2006153002/ )
Author  : ccameron
Commit description:
  
Reason for revert:
The patch that this depended on, https://codereview.chromium.org/1993333002/, has landed.

Original issue's description:
> Revert of Add logic to ResourceProvider to correctly lock GpuMemoryBuffer Resources. (patchset #8 id:140001 of https://codereview.chromium.org/1984873002/ )
>
> Reason for revert:
> Depending on an implementation still in review. Results in flooding of LOG messages.
>
> https://bugs.chromium.org/p/chromium/issues/detail?id=614155
> https://codereview.chromium.org/1993333002/
>
> Original issue's description:
> > Add logic to ResourceProvider to correctly lock GpuMemoryBuffer Resources.
> >
> > The new logic will hold onto GpuMemoryBuffer Resources until they are no longer
> > in use by the Window Server.
> >
> > BUG= 608026 
> > CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
> >
> > Committed: https://crrev.com/87aa976eacd8ed0c530d32a7c85d6ba706dcabf6
> > Cr-Commit-Position: refs/heads/master@{#395150}
>
> TBR=ccameron@chromium.org
> # Not skipping CQ checks because original CL landed more than 1 days ago.
> BUG= 608026 
>
> Committed: https://crrev.com/aa5126ff66379a9060e87b010135f1aee7fc1ab2
> Cr-Commit-Position: refs/heads/master@{#395524}

TBR=erikchen@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG= 608026 

Review-Url: https://codereview.chromium.org/2015923003
Cr-Commit-Position: refs/heads/master@{#396233}
Commit  : f8a942fbb35c30edcc88cfe859ceda7b469096af
Date    : Thu May 26 18:25:28 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@396217  303.2    10.3537  5  good
chromium@396227  305.0    7.0      5  good
chromium@396232  305.375  7.90908  8  good
chromium@396233  327.0    1.87083  5  bad    <--
chromium@396234  330.8    2.58844  5  bad
chromium@396235  324.5    7.17137  8  bad
chromium@396237  326.2    8.52643  5  bad
chromium@396256  328.4    4.77493  5  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 616513

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests power.gpu_rasterization.top_10
Test Metric: idle_wakeups_total/idle_wakeups_total
Relative Change: 8.31%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/649
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9011037889103571552


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

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