Android webview fix gpu crashes after destroy

content/common/gpu/gpu_command_buffer_stub.cc

Index: content/common/gpu/gpu_command_buffer_stub.cc
diff --git a/content/common/gpu/gpu_command_buffer_stub.cc b/content/common/gpu/gpu_command_buffer_stub.cc
index a8bb1c58d2379139a0cc52d36d18dd465f57d600..b536cb037ba5e22f4735bba21b8496d69cf4a074 100644
--- a/content/common/gpu/gpu_command_buffer_stub.cc
+++ b/content/common/gpu/gpu_command_buffer_stub.cc
@@ -426,7 +426,7 @@ void GpuCommandBufferStub::OnInitialize(
       // Need to adjust at least GLX to be able to create the initial context
       // with a config that is compatible with onscreen and offscreen surfaces.
       context = NULL;
-      LOG(FATAL) << "Failed to initialize virtual GL context.";
+      LOG(ERROR) << "Failed to initialize virtual GL context.";

[no sievers, 2013/01/25 20:24:41]

I don't really like removing the LOG(FATAL). I think we want to make sure that
on a platform that uses virtual contexts, it always works to create a virtual
context, which basically comes down to being able to make different surfaces
current with the same context (there's a known issue on Linux to make this work
at least).
It's scary to allow a mix of contexts, where we sometimes fail to share a real
context. We then end up not knowing what we are really running and that will
make it hard to deal with share-group related bugs.

Is this change needed if we correctly fail surface creation for which we should
bail out above in line 404? Do you know why this would fail here?

[boliu, 2013/01/25 21:27:02]

I didn't understand much of this, but sounds like this is the wrong fix. So
sounds like it should fall into line 404? I'll see what I can do. And I'll post
the stack trace for this one to the bug.

     } else {
       LOG(INFO) << "Created virtual GL context.";
     }