Fix some shutdown problems in tab capture performance tests.

chrome/browser/extensions/api/tab_capture/tab_capture_performancetest.cc

Index: chrome/browser/extensions/api/tab_capture/tab_capture_performancetest.cc
diff --git a/chrome/browser/extensions/api/tab_capture/tab_capture_performancetest.cc b/chrome/browser/extensions/api/tab_capture/tab_capture_performancetest.cc
index c3b720eb78fb12d555ea0353c9625e778ece2c2d..a86e94ebfeb0c5a78e7a8692144ef4631259c6b5 100644
--- a/chrome/browser/extensions/api/tab_capture/tab_capture_performancetest.cc
+++ b/chrome/browser/extensions/api/tab_capture/tab_capture_performancetest.cc
@@ -187,7 +187,7 @@ class TabCapturePerformanceTest
     // Ideally we'd like to run a higher capture rate when vsync is disabled,
     // but libjingle currently doesn't allow that.
     // page += HasFlag(kDisableVsync) ? "&fps=300" : "&fps=30";
-    page += "&fps=30";
+    page += "&fps=60";
     ASSERT_TRUE(RunExtensionSubtest("tab_capture", page)) << message_;
     ASSERT_TRUE(tracing::EndTracing(&json_events));
     scoped_ptr<trace_analyzer::TraceAnalyzer> analyzer;