Rebind EGL context to flush driver caches.

content/browser/android/in_process/synchronous_compositor_output_surface.cc

Index: content/browser/android/in_process/synchronous_compositor_output_surface.cc
diff --git a/content/browser/android/in_process/synchronous_compositor_output_surface.cc b/content/browser/android/in_process/synchronous_compositor_output_surface.cc
index 23de34af44af1f889309b78ade6a5e0ab528be1d..ad18d2694540958332adff0e146ee88cb0d6e36d 100644
--- a/content/browser/android/in_process/synchronous_compositor_output_surface.cc
+++ b/content/browser/android/in_process/synchronous_compositor_output_surface.cc
@@ -258,6 +258,7 @@ void SynchronousCompositorOutputSurface::SetMemoryPolicy(size_t bytes_limit) {
     // when this compositor is put into the background.
     context_provider()->ContextSupport()->SetAggressivelyFreeResources(
         true /* aggressively_free_resources */);
+    context_provider()->ContextGL()->FlushDriverCachesCHROMIUM();

[piman, 2015/07/13 21:25:29]

Should we do this before SetAggressivelyFreeResources?
Otherwise:
- SetAggressivelyFreeResources finished, and freed the command buffer
- FlushDriverCachesCHROMIUM reallocates the command buffer to put the command
in, and doesn't flush - so it won't actually happen until the next Flush, and we
still hold on to the command buffer memory in the mean time.

Either that or it could even be done inside of SetAggressivelyFreeResources.


Separately, don't we want to do this also for the !webview case, i.e. the other
places we call SetAggressivelyFreeResources?

[ericrk, 2015/07/13 22:11:11]

Moved this to FreeEverything.

   } else if (became_non_zero) {
     context_provider()->ContextSupport()->SetAggressivelyFreeResources(
         false /* aggressively_free_resources */);