There is a bug where the referenced surfaces gets updated after CompositorFrameSinkSupport::SubmitCompositorFrame() correctly then at the next LayerTreeHostImpl::BeginCommit() the references all get cleared. This only seems to happen when using DirectCompositorFrameSink, probably because MojoCompositorFrameSink doesn't have a ForceReclaimResources.

The following stack trace roughly outlines the problem:
SurfaceFactoryClient::ReferencedSurfacesChanged
Surface::ActivateFrame
Surface::QueueFrame
Surface::EvictFrame
SurfaceFactory::ClearSurface
CompositorFrameSinkSupport::ForceReclaimResources
DirectCompositorFrameSink::ForceReclaimResources
LayerTreeHostImpl::BeginCommit

This breaks the ability to use surface references for GC, since references may or may not exist depending on the timing. This effects  normal Chrome which is using sequences + references to find the set of live surfaces

There are enough SurfaceSequences being added to stop flashing on resize but I'd imagine this could cause some subtle problems.