Add flag to crash GPU process on hang.

Chromium developers should be able to try and use this flag to cause crash reports and see what's causing hangs.

BUG=


Review URL: https://chromiumcodereview.appspot.com/11191020

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@162792 0039d316-1c4b-4281-b951-d872f2087c98

2 files changed, 5 insertions, 0 deletions

diff --git a/content/public/common/content_switches.cc b/content/public/common/content_switches.cc
index 1ddae70..1c5b759 100644
--- a/content/public/common/content_switches.cc
+++ b/content/public/common/content_switches.cc
@@ -36,6 +36,10 @@ const char kBrowserSubprocessPath[]         = "browser-subprocess-path";
 // as a dependent process of the Chrome Frame plugin.
 const char kChromeFrame[]                   = "chrome-frame";
 
+// Cause a GPU hang to cause a crash dump, allowing for easier debugging of
+// them.
+const char kCrashOnGpuHang[]                = "crash-on-gpu-hang";
+
 // Disables client-visible 3D APIs, in particular WebGL and Pepper 3D.
 // This is controlled by policy and is kept separate from the other
 // enable/disable switches to avoid accidentally regressing the policy
diff --git a/content/public/common/content_switches.h b/content/public/common/content_switches.h
index 891b20d..4de3819 100644
--- a/content/public/common/content_switches.h
+++ b/content/public/common/content_switches.h
@@ -22,6 +22,7 @@ CONTENT_EXPORT extern const char kBrowserCrashTest[];
 CONTENT_EXPORT extern const char kBrowserSubprocessPath[];
 // TODO(jam): this doesn't belong in content.
 CONTENT_EXPORT extern const char kChromeFrame[];
+CONTENT_EXPORT extern const char kCrashOnGpuHang[];
 CONTENT_EXPORT extern const char kDisable3DAPIs[];
 CONTENT_EXPORT extern const char kDisableAccelerated2dCanvas[];
 CONTENT_EXPORT extern const char kDisableAcceleratedCompositing[];