summaryrefslogtreecommitdiffstats
path: root/content/browser
diff options
context:
space:
mode:
authorzmo@google.com <zmo@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2011-11-09 23:16:12 +0000
committerzmo@google.com <zmo@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2011-11-09 23:16:12 +0000
commit663ef09409998887174b51b1e9c1c70f9b9eb93c (patch)
tree1cfadae7e42d3e5fe1d8e85c4c95b90c46c337ba /content/browser
parent8df769e694b0a19d0768ba70e5c90eed9fb70a71 (diff)
downloadchromium_src-663ef09409998887174b51b1e9c1c70f9b9eb93c.zip
chromium_src-663ef09409998887174b51b1e9c1c70f9b9eb93c.tar.gz
chromium_src-663ef09409998887174b51b1e9c1c70f9b9eb93c.tar.bz2
Add tests to make sure gpu blacklist actually block gpu features.
The general idea is to use jbates's newly added tracing: if a feature is blacklisted, we check the tracing data to make sure gpu process hasn't launched. BUG=101222 TEST=browser_tests Review URL: http://codereview.chromium.org/8497034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109328 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/browser')
-rw-r--r--content/browser/gpu/gpu_process_host.cc2
1 files changed, 2 insertions, 0 deletions
diff --git a/content/browser/gpu/gpu_process_host.cc b/content/browser/gpu/gpu_process_host.cc
index 0612fca..fade001a 100644
--- a/content/browser/gpu/gpu_process_host.cc
+++ b/content/browser/gpu/gpu_process_host.cc
@@ -467,6 +467,8 @@ void GpuProcessHost::OnProcessLaunched() {
// respond to any requests to establish a GPU channel. The response
// to such requests require that the GPU process handle be known.
+ TRACE_EVENT0("test_gpu", "GpuProcessLaunched");
+
base::ProcessHandle child_handle = in_process_ ?
base::GetCurrentProcessHandle() : handle();