GitLab

Relying on browser compositor for the reset is problematic because
reset stops if app is in the background, which also happen to be the
time the GPU is most likely to be killed by Android.

Move the reset signal to any context creation success directly from
the GPU process. ContextProviderCommandBuffer::BindToCurrentThread
does more things like registering transfer buffers. But hopefully
those don't cause GPU crashes.

Bug: 777601
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
Change-Id: I360c29c97c7a3222a84cb797c8be2f3fb65200db
Reviewed-on: https://chromium-review.googlesource.com/786271Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Commit-Queue: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519869}