Updates:
Summary: All request contexts are leaked when using extensions
Owner: mpcompl...@chromium.org
Cc: ero...@chromium.org
Labels: -Mstone-5 Mstone-4
Comment #14 on issue 15708 by ero...@chromium.org: All request contexts are
leaked when using extensions
http://code.google.com/p/chromium/issues/detail?id=15708
Ok, so I finally got around to debugging this (its a pain to track stray
ref-counts).
I am able to reproduce the leak 100%, provided I am using extensions
If I have no extensions installed, no leaks.
Specifically, here is what happens:
ExtensionHost:CreateRenderView() creates a new ResourceMessageFilter.
The filter holds a reference to all of the request contexts.
Unfortunately, the ResourceMessageFilter is never being destroyed. This in
turn means that all the request contexts
stay references, and also leak!
Back over to mpcomplete to figure out the extension side of this.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
