Revert of Remove ForceReclaimResources

Revert of Remove ForceReclaimResources (patchset #8 id:170001 of https://codereview.chromium.org/2609253003/ )

Reason for revert:
This has introduced flakiness into TextureLayerImplWithMailboxThreadedCallback.RunMultiThread_DelegatingRenderer, will address this and re-land.

Original issue's description:
> Remove ForceReclaimResources
> 
> We had previously added ForceReclaimResources to BeginCommit to throttle
> frame output and prevent starving the display compositor's rasterization
> tasks. Unfortunately, this introduces significant overhead as well.
> 
> With the addition of the Display Scheduler, this change no longer
> appears to be needed. The scheduler has independent controls for
> limiting the number of pending frames, and these should be used instead
> (if further tweaking is necessary).
> 
> Removing this logic does not regress the benchmarks which it was
> initially added for, and seems unneeded at this point. Removing.
> 
> R=reveman@chromium.org
> BUG=676852, 489515, 617268
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
> 
> Review-Url: https://codereview.chromium.org/2609253003
> Cr-Commit-Position: refs/heads/master@{#443061}
> Committed: https://chromium.googlesource.com/chromium/src/+/dc1892fc0639464d4418ccfaedfd1f95a5b947d0

TBR=reveman@chromium.org,danakj@chromium.org,enne@chromium.org,tommi@chromium.org,brianderson@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=676852, 489515, 617268, 681093, 680770
Review-Url: https://codereview.chromium.org/2633563003
Cr-Commit-Position: refs/heads/master@{#443709}
Committed: https://chromium.googlesource.com/chromium/src/+/4b443521bc4bc46b4bd1537910f089fbf1578273

[ericrk, 2017-01-13 20:41:16]

The CQ bit was checked by ericrk@chromium.org

[ericrk, 2017-01-13 20:41:16]

Created Revert of Remove ForceReclaimResources

[commit-bot: I haz the power, 2017-01-13 20:42:09]

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

[ericrk, 2017-01-13 20:42:14]

Description was changed from

==========
Revert of Remove ForceReclaimResources (patchset #8 id:170001 of
https://codereview.chromium.org/2609253003/ )

Reason for revert:
This has introduced flakiness into
TextureLayerImplWithMailboxThreadedCallback.RunMultiThread_DelegatingRenderer,
will address this and re-land.

Original issue's description:
> Remove ForceReclaimResources
> 
> We had previously added ForceReclaimResources to BeginCommit to throttle
> frame output and prevent starving the display compositor's rasterization
> tasks. Unfortunately, this introduces significant overhead as well.
> 
> With the addition of the Display Scheduler, this change no longer
> appears to be needed. The scheduler has independent controls for
> limiting the number of pending frames, and these should be used instead
> (if further tweaking is necessary).
> 
> Removing this logic does not regress the benchmarks which it was
> initially added for, and seems unneeded at this point. Removing.
> 
> R=reveman@chromium.org
> BUG=676852,489515,617268
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
> 
> Review-Url: https://codereview.chromium.org/2609253003
> Cr-Commit-Position: refs/heads/master@{#443061}
> Committed:
https://chromium.googlesource.com/chromium/src/+/dc1892fc0639464d4418ccfaedfd...

TBR=reveman@chromium.org,danakj@chromium.org,enne@chromium.org,tommi@chromium...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=676852,489515,617268
==========

to

==========
Revert of Remove ForceReclaimResources (patchset #8 id:170001 of
https://codereview.chromium.org/2609253003/ )

Reason for revert:
This has introduced flakiness into
TextureLayerImplWithMailboxThreadedCallback.RunMultiThread_DelegatingRenderer,
will address this and re-land.

Original issue's description:
> Remove ForceReclaimResources
> 
> We had previously added ForceReclaimResources to BeginCommit to throttle
> frame output and prevent starving the display compositor's rasterization
> tasks. Unfortunately, this introduces significant overhead as well.
> 
> With the addition of the Display Scheduler, this change no longer
> appears to be needed. The scheduler has independent controls for
> limiting the number of pending frames, and these should be used instead
> (if further tweaking is necessary).
> 
> Removing this logic does not regress the benchmarks which it was
> initially added for, and seems unneeded at this point. Removing.
> 
> R=reveman@chromium.org
> BUG=676852,489515,617268
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
> 
> Review-Url: https://codereview.chromium.org/2609253003
> Cr-Commit-Position: refs/heads/master@{#443061}
> Committed:
https://chromium.googlesource.com/chromium/src/+/dc1892fc0639464d4418ccfaedfd...

TBR=reveman@chromium.org,danakj@chromium.org,enne@chromium.org,tommi@chromium...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=676852,489515,617268, 681093, 680770
==========

[commit-bot: I haz the power, 2017-01-13 22:54:28]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1484340076019360, "parent_rev":
"9f47425664522cc66295d3e5837e3ad07acd6241", "commit_rev":
"4b443521bc4bc46b4bd1537910f089fbf1578273"}

[commit-bot: I haz the power, 2017-01-13 22:54:58]

Description was changed from

==========
Revert of Remove ForceReclaimResources (patchset #8 id:170001 of
https://codereview.chromium.org/2609253003/ )

Reason for revert:
This has introduced flakiness into
TextureLayerImplWithMailboxThreadedCallback.RunMultiThread_DelegatingRenderer,
will address this and re-land.

Original issue's description:
> Remove ForceReclaimResources
> 
> We had previously added ForceReclaimResources to BeginCommit to throttle
> frame output and prevent starving the display compositor's rasterization
> tasks. Unfortunately, this introduces significant overhead as well.
> 
> With the addition of the Display Scheduler, this change no longer
> appears to be needed. The scheduler has independent controls for
> limiting the number of pending frames, and these should be used instead
> (if further tweaking is necessary).
> 
> Removing this logic does not regress the benchmarks which it was
> initially added for, and seems unneeded at this point. Removing.
> 
> R=reveman@chromium.org
> BUG=676852,489515,617268
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
> 
> Review-Url: https://codereview.chromium.org/2609253003
> Cr-Commit-Position: refs/heads/master@{#443061}
> Committed:
https://chromium.googlesource.com/chromium/src/+/dc1892fc0639464d4418ccfaedfd...

TBR=reveman@chromium.org,danakj@chromium.org,enne@chromium.org,tommi@chromium...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=676852,489515,617268, 681093, 680770
==========

to

==========
Revert of Remove ForceReclaimResources (patchset #8 id:170001 of
https://codereview.chromium.org/2609253003/ )

Reason for revert:
This has introduced flakiness into
TextureLayerImplWithMailboxThreadedCallback.RunMultiThread_DelegatingRenderer,
will address this and re-land.

Original issue's description:
> Remove ForceReclaimResources
> 
> We had previously added ForceReclaimResources to BeginCommit to throttle
> frame output and prevent starving the display compositor's rasterization
> tasks. Unfortunately, this introduces significant overhead as well.
> 
> With the addition of the Display Scheduler, this change no longer
> appears to be needed. The scheduler has independent controls for
> limiting the number of pending frames, and these should be used instead
> (if further tweaking is necessary).
> 
> Removing this logic does not regress the benchmarks which it was
> initially added for, and seems unneeded at this point. Removing.
> 
> R=reveman@chromium.org
> BUG=676852,489515,617268
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
> 
> Review-Url: https://codereview.chromium.org/2609253003
> Cr-Commit-Position: refs/heads/master@{#443061}
> Committed:
https://chromium.googlesource.com/chromium/src/+/dc1892fc0639464d4418ccfaedfd...

TBR=reveman@chromium.org,danakj@chromium.org,enne@chromium.org,tommi@chromium...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=676852,489515,617268, 681093, 680770

Review-Url: https://codereview.chromium.org/2633563003
Cr-Commit-Position: refs/heads/master@{#443709}
Committed:
https://chromium.googlesource.com/chromium/src/+/4b443521bc4bc46b4bd1537910f0...
==========

[commit-bot: I haz the power, 2017-01-13 22:54:59]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/4b443521bc4bc46b4bd1537910f0...