This is a tracking bug for replacing all usage of SurfaceSequence with SurfaceReference and ultimately deleting SurfaceSequences. As mentioned here https://go/surface-lifetime-management SurfaceSequences aren't really a good fit for an out-of-process display compositor.
Here's roughly the work I think needs to get done.
1. SurfaceReference derives from SurfaceReferenceBase.
2. Write a surface_reference_factory.mojom or something that creates references or destroys references. Implement a MojoSurfaceReferenceFactory (I hate that name, blah). MojoCompositorFrameSink dispenses a MojoSurfaceReferenceFactory associated interface.
3. Replace all SurfaceReferenceFactory implementations with MojoSurfaceReferenceFactory.
4. Delete SurfaceSequence, all associated SurfaceReferences and SurfaceReferenceFactories, and cleanup SurfaceManager.
Comment 1 by fsam...@chromium.org
, Jan 10 2017Owner: samans@chromium.org
Status: Assigned (was: Untriaged)