Register SharedMemory through CompositorFrameSink for OffscreenCanavas
This converts from using the SharedBitmapManager, which registers shared memory through its own parallel channel, to allocating SharedMemory directly and reporting it to the CompositorFrameSink. The SharedBitmapManager path was racey with the submission of CompositorFrames, unless sequence numbers were used (they were not in this code), and required the display compositor to live in the browser process. With this change, OffscreenCanvas will work with viz software compositing. R=kylechar@chromium.org Bug: 730660 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I0daa654112e9834a325754ade37d19325793e01e Reviewed-on: https://chromium-review.googlesource.com/1017316Reviewed-by:Justin Novosad <junov@chromium.org> Reviewed-by:
kylechar <kylechar@chromium.org> Commit-Queue: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#552106}
Showing
Please register or sign in to comment