sync compositor: handle gpu thread context loss |
||
Issue descriptionLooking into it today. Semi-involved. Need to add output_surface_id and keep track of it for resources, so that resources for lost output surface don't go to the new one. Then it's relatively simple to not tear down everything on the renderer side when the output surface goes away.
,
Mar 23 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7c1bd415bfbed8d80249a4e25788fbe967c97699 commit 7c1bd415bfbed8d80249a4e25788fbe967c97699 Author: boliu <boliu@chromium.org> Date: Wed Mar 23 23:50:10 2016 sync compositor: Handle context loss OutputSurface becomes a mutable part of SynchronousCompositorProxy. Proxy needes to make sure access to OutputSurface are null checked. And the Registry (ie SynchronousCompositorFilter) need to treat the OutputSurface part as an optional part of Proxy init. BUG= 592744 Review URL: https://codereview.chromium.org/1773873002 Cr-Commit-Position: refs/heads/master@{#382978} [modify] https://crrev.com/7c1bd415bfbed8d80249a4e25788fbe967c97699/content/renderer/android/synchronous_compositor_filter.cc [modify] https://crrev.com/7c1bd415bfbed8d80249a4e25788fbe967c97699/content/renderer/android/synchronous_compositor_output_surface.cc [modify] https://crrev.com/7c1bd415bfbed8d80249a4e25788fbe967c97699/content/renderer/android/synchronous_compositor_output_surface.h [modify] https://crrev.com/7c1bd415bfbed8d80249a4e25788fbe967c97699/content/renderer/android/synchronous_compositor_proxy.cc [modify] https://crrev.com/7c1bd415bfbed8d80249a4e25788fbe967c97699/content/renderer/android/synchronous_compositor_proxy.h
,
Mar 24 2016
,
Jun 3 2016
Issue 617165 has been merged into this issue. |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Mar 22 2016