Record event activity to the extension activity log.

chrome/browser/extensions/api/web_request/web_request_api.cc

Index: chrome/browser/extensions/api/web_request/web_request_api.cc
diff --git a/chrome/browser/extensions/api/web_request/web_request_api.cc b/chrome/browser/extensions/api/web_request/web_request_api.cc
index a1e07b23da5fceccc4d935b099bb64a640dc4f50..0337da177a76bd614a643db554af15eb721b4f88 100644
--- a/chrome/browser/extensions/api/web_request/web_request_api.cc
+++ b/chrome/browser/extensions/api/web_request/web_request_api.cc
@@ -1078,7 +1078,8 @@ bool ExtensionWebRequestEventRouter::DispatchEvent(
       dict->Remove(keys::kResponseHeadersKey, NULL);
 
     extensions::EventRouter::DispatchEvent(
-        (*it)->ipc_sender.get(), (*it)->extension_id, (*it)->sub_event_name,
+        (*it)->ipc_sender.get(), static_cast<Profile*>(profile),

[Matt Perry, 2013/01/25 21:24:17]

There's a reason that |profile| is a void* - so you don't end up dereferencing
it like this :). This is on the IO thread. Even though you're pinging it over to
the UI thread eventually, it's not safe because there's no guarantee the Profile
hasn't been deleted by the time you dereference it.

See
https://code.google.com/p/chromium/codesearch#chrome/src/chrome/browser/net/c...
for the (hacky) way to handle this case. I'd prefer you keep the profile as a
void* until it makes its way all the way to the UI thread.

[mvrable, 2013/01/28 16:27:36]

Fixed I think--does the new version look all right?

+        (*it)->extension_id, (*it)->sub_event_name,
         args_filtered.Pass(), GURL(),
         extensions::EventRouter::USER_GESTURE_UNKNOWN,
         extensions::EventFilteringInfo());