cc: Get rid of PostSwapBuffersComplete.

content/browser/compositor/vulkan_browser_compositor_output_surface.cc

Index: content/browser/compositor/vulkan_browser_compositor_output_surface.cc
diff --git a/content/browser/compositor/vulkan_browser_compositor_output_surface.cc b/content/browser/compositor/vulkan_browser_compositor_output_surface.cc
index b06f9f22ab6192d2310a4c66ca07d9c03a67ad05..07d81aeab931763f26cf2b882e0bcf7e013def2a 100644
--- a/content/browser/compositor/vulkan_browser_compositor_output_surface.cc
+++ b/content/browser/compositor/vulkan_browser_compositor_output_surface.cc
@@ -48,13 +48,12 @@ void VulkanBrowserCompositorOutputSurface::OnGpuSwapBuffersCompleted(
     gfx::SwapResult result,
     const gpu::GpuProcessHostedCALayerTreeParamsMac* params_mac) {
   RenderWidgetHostImpl::CompositorFrameDrawn(latency_info);
-  OnSwapBuffersComplete();
+  client_->DidSwapBuffersComplete();
 }
 
 void VulkanBrowserCompositorOutputSurface::SwapBuffers(
     cc::CompositorFrame* frame) {
   surface_->SwapBuffers();
-  PostSwapBuffersComplete();

[boliu, 2016/10/09 22:55:08]

was the previous thing calling DidSwapBuffersComplete twice per frame? by
mistake?

[danakj, 2016/10/10 20:28:19]

I think so but this was never seriously run yet, it may be that
OnGpuSwapBuffersCompleted isn't hooked up, but we'll find that out quickly
if/when we use this class again.

 }
 
 }  // namespace content