Correctly destroy returned front buffer after resize

Correctly destroy returned front buffer after resize

When returning a front buffer with ReturnFrontBuffer, if the front buffer was
resized in the mean time, we were considering the returned mailbox as lost, and
never freeing it, causing a large GPU memory leak.
This patch fixes it.

BUG=692074
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;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

Review-Url: https://codereview.chromium.org/2779873002
Cr-Commit-Position: refs/heads/master@{#459969}
(cherry picked from commit 15176a8d134862de21fe2de9f9fd1d7390ac9003)

Review-Url: https://codereview.chromium.org/2783203004 .
Cr-Commit-Position: refs/branch-heads/3029@{#495}
Cr-Branched-From: 939b32ee5ba05c396eef3fd992822fcca9a2e262-refs/heads/master@{#454471}
Committed: https://chromium.googlesource.com/chromium/src/+/49aa6162abfe9749ead405c8f593abdea54ad630

[piman, 2017-03-30 18:57:19]

Description was changed from

==========
Correctly destroy returned front buffer after resize

When returning a front buffer with ReturnFrontBuffer, if the front buffer was
resized in the mean time, we were considering the returned mailbox as lost, and
never freeing it, causing a large GPU memory leak.
This patch fixes it.

BUG=692074
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;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

Review-Url: https://codereview.chromium.org/2779873002
Cr-Commit-Position: refs/heads/master@{#459969}
(cherry picked from commit 15176a8d134862de21fe2de9f9fd1d7390ac9003)
==========

to

==========
Correctly destroy returned front buffer after resize

When returning a front buffer with ReturnFrontBuffer, if the front buffer was
resized in the mean time, we were considering the returned mailbox as lost, and
never freeing it, causing a large GPU memory leak.
This patch fixes it.

BUG=692074
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;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

Review-Url: https://codereview.chromium.org/2779873002
Cr-Commit-Position: refs/heads/master@{#459969}
(cherry picked from commit 15176a8d134862de21fe2de9f9fd1d7390ac9003)

Review-Url: https://codereview.chromium.org/2783203004 .
Cr-Commit-Position: refs/branch-heads/3029@{#495}
Cr-Branched-From:
939b32ee5ba05c396eef3fd992822fcca9a2e262-refs/heads/master@{#454471}
Committed:
https://chromium.googlesource.com/chromium/src/+/49aa6162abfe9749ead405c8f593...
==========

[piman, 2017-03-30 18:57:20]

Committed patchset #1 (id:1) manually as
49aa6162abfe9749ead405c8f593abdea54ad630.