Android WebView: Crash on compositor context loss

android_webview/browser/aw_render_thread_context_provider.cc

Index: android_webview/browser/aw_render_thread_context_provider.cc
diff --git a/android_webview/browser/aw_render_thread_context_provider.cc b/android_webview/browser/aw_render_thread_context_provider.cc
index 748de1f3e510d81c4d6b54beacd43cf4deb5acfa..acc6e36f290efc21c1408298a8eba6788a268c51 100644
--- a/android_webview/browser/aw_render_thread_context_provider.cc
+++ b/android_webview/browser/aw_render_thread_context_provider.cc
@@ -59,7 +59,7 @@ AwRenderThreadContextProvider::AwRenderThreadContextProvider(
   gpu::gles2::ContextCreationAttribHelper attribs_for_gles2;
   gpu_blink::WebGraphicsContext3DImpl::ConvertAttributes(attributes,
                                                          &attribs_for_gles2);
-  attribs_for_gles2.lose_context_when_out_of_memory = true;
+  attribs_for_gles2.lose_context_when_out_of_memory = false;

[no sievers, 2015/11/18 23:50:20]

nit: maybe put a comment that this is not our context but the framework's, so
not up to us to decide when to lose it

speaking of which: do we handle the framework allocating a new context?

 
   context_.reset(gpu::GLInProcessContext::Create(
       service,