=== Auto-CCing suspected CL author jbauman@chromium.org ===
Hi jbauman@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 : jbauman
Commit : 5b05b9032e67ea278ae3a3d1eb2731d1dcdb68c5
Date : Thu Aug 10 06:02:54 2017
Subject: Allow creating GLImage-backed textures with glTexStorage2D.
Bisect Details
Configuration: mac_10_11_perf_bisect
Benchmark : media.tough_video_cases_tbmv2
Metric : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/video.html?src_garden2_10s.webm_seek
Change : 10.95% | 9001736.0 -> 9987128.0
Revision Result N
chromium@493236 9001736 +- 0.0 6 good
chromium@493292 9001736 +- 0.0 6 good
chromium@493299 9001736 +- 0.0 6 good
chromium@493301 9001736 +- 0.0 6 good
chromium@493302 9987128 +- 0.0 6 bad <--
chromium@493303 9987128 +- 0.0 6 bad
chromium@493306 9987128 +- 0.0 6 bad
chromium@493320 9987128 +- 0.0 6 bad
chromium@493347 9987128 +- 0.0 6 bad
To Run This Test
src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.garden2.10s.webm.seek media.tough_video_cases_tbmv2
More information on addressing performance regressions:
http://g.co/ChromePerformanceRegressions
Debug information about this bisect:
https://chromeperf.appspot.com/buildbucket_job_status/8971276603994965824
For feedback, file a bug with component Speed>Bisection
jbauman no longer works on Chrome, but it will be a pity this CL doesn't land. We need someone else pick this up and figure out why the memory increase.
The original change was reverted, but a slightly different implementation of the same idea was landed in crrev.com/c/714654 and crrev.com/c/625064. That caused a regression too (although we believe it's a memory tracking issue and not a real regression) which is tracked in issue 780510 .
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 14 2017