Report active extensions in crash reports. This only implements Windows right now. Mac and linux will be separate CLs.

"Active" is overloaded to mean different things depending on
the process type:

- browser: all enabled extensions
- renderer: unique set of extensions from all user scripts
- extension: extensions running in the process

BUG=27169

Review URL: http://codereview.chromium.org/437078

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

1 files changed, 8 insertions, 0 deletions

diff --git a/chrome/browser/renderer_host/browser_render_process_host.cc b/chrome/browser/renderer_host/browser_render_process_host.cc
index db701ab..1bf6aa0 100644
--- a/chrome/browser/renderer_host/browser_render_process_host.cc
+++ b/chrome/browser/renderer_host/browser_render_process_host.cc
@@ -587,6 +587,14 @@ void BrowserRenderProcessHost::InitExtensions() {
 
 void BrowserRenderProcessHost::SendUserScriptsUpdate(
     base::SharedMemory *shared_memory) {
+  // Don't send user scripts to extension processes. We currently don't allow
+  // user scripts to run in extensions, so it would be pointless. It would also
+  // mess up the crash reporting, which sends a different set of "active"
+  // extensions depending on whether the process is an extension or renderer
+  // process.
+  if (extension_process_)
+    return;
+
   // Process is being started asynchronously.  We'll end up calling
   // InitUserScripts when it's created which will call this again.
   if (child_process_.get() && child_process_->IsStarting())