Add gpu command buffer support for loseContextCHROMIUM

content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.cc

Index: content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.cc
diff --git a/content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.cc b/content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.cc
index ed105b4fe93c19225e424538c4ebfe528e8657c7..69f0947ac6aca6cfd4484347a436ec722e9b2cdd 100644
--- a/content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.cc
+++ b/content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.cc
@@ -1599,6 +1599,13 @@ void WebGraphicsContext3DCommandBufferImpl::signalSyncPoint(
       base::Bind(&SignalSyncPointCallback, base::Passed(&own_callback)));
 }
 
+void WebGraphicsContext3DCommandBufferImpl::loseContextCHROMIUM(
+    WGC3Denum current, WGC3Denum other) {
+  gl_->LoseContextCHROMIUM(current, other);
+  gl_->Finish();

[piman, 2013/06/21 19:05:05]

Actually, doing a Finish() here makes it less interesting as far as testing
goes, I would replace it by a Flush().

In production, context loss will always be asynchronous, and 95% of the issues
are to deal with that asynchronicity.

If some given tests really need a synchronous behavior, they can call finish()
directly.

+  DCHECK(IsCommandBufferContextLost());
+}
+
 void WebGraphicsContext3DCommandBufferImpl::genMailboxCHROMIUM(
     WGC3Dbyte* name) {
   std::vector<gpu::Mailbox> names(1);