GitLab

A surface may stay alive after its CompositorFrameSink is thrown away.
This can happen if the surface is referenced by a parent compositor.

A new child CompositorFrameSink may be created (after context lost)
and it may reuse the same surface before it is garbage collected.
In this case, the surface refers to an invalid SurfaceClient
(CompositorFrameSinkSuppport), and crashes. This CL fixes the issue.

Bug: 791172
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I7814bf40b706c52d755fdd69accce1deee9862a0
Reviewed-on: https://chromium-review.googlesource.com/818126Reviewed-by: Saman Sami <samans@chromium.org>
Commit-Queue: Fady Samuel <fsamuel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523199}