DCHECK if shader compilation fails that it's due to context loss.

gpu/command_buffer/client/gles2_implementation.cc

Index: gpu/command_buffer/client/gles2_implementation.cc
diff --git a/gpu/command_buffer/client/gles2_implementation.cc b/gpu/command_buffer/client/gles2_implementation.cc
index 7708bc129c7aec036cc6186e7ab3d128beec0a79..de284b5ac93da521321e23458a6b64de25729fce 100644
--- a/gpu/command_buffer/client/gles2_implementation.cc
+++ b/gpu/command_buffer/client/gles2_implementation.cc
@@ -5371,6 +5371,10 @@ void GLES2Implementation::RetireSyncPointCHROMIUM(GLuint sync_point) {
   gpu_control_->RetireSyncPoint(sync_point);
 }
 
+bool GLES2Implementation::IsContextLost() {
+  return helper_->IsContextLost();

[Ken Russell (switch to Gerrit), 2015/05/29 17:47:05]

Per piman's comment --
WebGraphicsContext3DCommandBufferImpl::IsCommandBufferContextLost checks the GPU
channel's state too. I wonder whether the propagation of context lost state from
the channel to all of the command buffers
(GpuCommandBufferStub::CheckContextLost and related code) will be enough to get
this bit set.

+}
+
 namespace {
 
 bool ValidImageFormat(GLenum internalformat,