Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(47)

Unified Diff: chrome/browser/renderer_host/browser_render_process_host.cc

Issue 437078: Report active extensions in crash reports (windows only). (Closed)
Patch Set: Rework Created 11 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: chrome/browser/renderer_host/browser_render_process_host.cc
diff --git a/chrome/browser/renderer_host/browser_render_process_host.cc b/chrome/browser/renderer_host/browser_render_process_host.cc
index db701ab54daa885fd75b30787b6be1e08e314d31..dd4d0efac8af6aa46b8263767ec44820af691b3c 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())

Powered by Google App Engine
This is Rietveld 408576698