ui: Reclaim shared main thread context resources

Desktop / Chromium - David Reveman [chromium.org] - 11 October 2017 23:15 EDT

Implement appropriate reclaim of resources created using the main thread context for exo and fast ink.

This is done by submitting an empty frame after the top level window as been destroyed and wanting for all previously submitted resources to be reclaimed.

Bug: 765763 Test: exo_unittests --gtest_filter=BufferTest.SurfaceTreeHostDestruction Change-Id: I31a123172d5a4a4b45fc3ccb2837e8455a4f61a8 Reviewed-on: https://chromium-review.googlesource.com/696648

f273350 ui: Reclaim shared main thread context resources.
ash/fast_ink/fast_ink_view.cc | 227 +++++++++++++++----------
ash/fast_ink/fast_ink_view.h | 25 +--
components/exo/buffer_unittest.cc | 47 +++++
components/exo/layer_tree_frame_sink_holder.cc | 88 +++++++++-
components/exo/layer_tree_frame_sink_holder.h | 34 +++-
components/exo/surface_tree_host.cc | 10 +-
6 files changed, 305 insertions(+), 126 deletions(-)

Upstream: git.chromium.org


  • Share