Iterative cleanup for GL programs in GPU process

Iterative cleanup for GL programs in GPU process

Currently, when we destroy a GPU channel, we delete all programs in
a single operation. This operation can be moderately expensive, and on
very overloaded systems (and with enough programs), may take more than
the 10s given to a task by the GPU watchdog.

This change allows programs to be iteratively deleted over several
tasks, allowing other GPU operations and IPCs to be processed, and
preventing us from timing out the watchdog timer.

This is an experimental CL to see if the crash rates in crbug.com/612219
are addressed. If so, more cleanup and additional iterative deletion
will be added.

BUG=612219
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

[ericrk, 2016-09-26 22:02:24]

Description was changed from

==========
Iterative cleanup for GL programs in GPU process

Currently, when we destroy a GPU channel, we delete all programs in
a single operation. This operation can be moderately expensive, and on
very overloaded systems (and with enough programs), may take more than
the 10s given to a task by the GPU watchdog.

This change allows programs to be iteratively deleted over several
tasks, allowing other GPU operations and IPCs to be processed, and
preventing us from timing out the watchdog timer.

This is an experimental CL to see if the crash rates in crbug.com/612219
are addressed. If so, more cleanup and additional iterative deletion
will be added.

BUG=612219
==========

to

==========
Iterative cleanup for GL programs in GPU process

Currently, when we destroy a GPU channel, we delete all programs in
a single operation. This operation can be moderately expensive, and on
very overloaded systems (and with enough programs), may take more than
the 10s given to a task by the GPU watchdog.

This change allows programs to be iteratively deleted over several
tasks, allowing other GPU operations and IPCs to be processed, and
preventing us from timing out the watchdog timer.

This is an experimental CL to see if the crash rates in crbug.com/612219
are addressed. If so, more cleanup and additional iterative deletion
will be added.

BUG=612219
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[ericrk, 2016-09-26 22:43:49]

The CQ bit was checked by ericrk@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-09-26 22:44:35]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-26 22:59:17]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-26 22:59:18]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[ericrk, 2016-09-26 23:13:36]

The CQ bit was checked by ericrk@chromium.org

[ericrk, 2016-09-26 23:13:39]

The CQ bit was unchecked by ericrk@chromium.org

[ericrk, 2016-09-26 23:13:43]

The CQ bit was checked by ericrk@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-09-26 23:14:06]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-26 23:23:11]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-26 23:23:12]

Dry run: Try jobs failed on following builders:
  linux_optional_gpu_tests_rel on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_optional_...)

[ericrk, 2016-09-26 23:45:00]

Patchset #3 (id:40001) has been deleted

[ericrk, 2016-09-26 23:45:05]

The CQ bit was checked by ericrk@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-09-26 23:45:40]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-27 01:17:06]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-27 01:17:06]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[ericrk, 2016-09-27 20:15:51]

The CQ bit was checked by ericrk@chromium.org

[commit-bot: I haz the power, 2016-09-27 20:16:18]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-27 20:16:18]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-27 20:16:20]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.