Randomly enable leak detector based on probability parameter

chrome/renderer/chrome_content_renderer_client.cc

Index: chrome/renderer/chrome_content_renderer_client.cc
diff --git a/chrome/renderer/chrome_content_renderer_client.cc b/chrome/renderer/chrome_content_renderer_client.cc
index 2b744c677ff3a4d66c089c88387b1ec46c5ba688..2002ba3e26a8fa65626379c1286db05c82bad67f 100644
--- a/chrome/renderer/chrome_content_renderer_client.cc
+++ b/chrome/renderer/chrome_content_renderer_client.cc
@@ -441,6 +441,11 @@ void ChromeContentRendererClient::RenderThreadStarted() {
     WebSecurityPolicy::addSchemeToBypassSecureContextWhitelist(
         WebString::fromUTF8(scheme));
   }
+
+#if defined(OS_CHROMEOS)
+  leak_detector_remote_client_.reset(new LeakDetectorRemoteClient());
+  thread->AddObserver(leak_detector_remote_client_.get());

[sadrul, 2016/08/08 20:20:06]

I was going to comment that there isn't a corresponding RemoveObserver, but
looks like that's the pattern for the rest of the observers added here (and
Remove isn't necessary right now either since the observer is destroyed only
when the thread itself is also destroyed).

+#endif
 }
 
 void ChromeContentRendererClient::RenderFrameCreated(