Windows: On context lost, GPU process exits.

gpu/command_buffer/service/feature_info.cc

Index: gpu/command_buffer/service/feature_info.cc
===================================================================
--- gpu/command_buffer/service/feature_info.cc	(revision 190356)
+++ gpu/command_buffer/service/feature_info.cc	(working copy)
@@ -97,6 +97,7 @@
       flush_on_context_switch(false),
       delete_instead_of_resize_fbo(false),
       use_client_side_arrays_for_stream_buffers(false),
+      exit_on_context_lost(false),
       max_texture_size(0),
       max_cube_map_texture_size(0) {
 }
@@ -701,6 +702,12 @@
     // TODO(dsinclair): Add AddExtensionString("GL_CHROMIUM_sampler_objects")
     // when available.
   }
+
+#if defined(OS_WIN)
+  // Some drivers are unable to reset the D3D device in the GPU process
+  // sandbox.
+  workarounds_.exit_on_context_lost = true;

[Ken Russell (switch to Gerrit), 2013/03/27 02:04:11]

It would be much better and more maintainable to set this flag from the GPU
blacklist. Is that feasible?

[Zhenyao Mo, 2013/03/27 02:53:54]

I just did some refactoring and the mechanism to do this in blacklist is ready. 
I am planning to move all the workarounds to blacklist (I call it driver bug
list).

This CL LGTM as it is.  Land this and I'll work on top of that.

+#endif
 }
 
 void FeatureInfo::AddExtensionString(const std::string& str) {