Comment #3 on issue 22020 by bcbryant: about:memory doesn't display extension processes properly http://code.google.com/p/chromium/issues/detail?id=22020
that fix didn't work for --single-process, so matching based on RenderViewHost is better. i.e. instead of: if ( process.pid == ((*ehost)->render_process_host()->process().pid()) ) do this: if ( host == (*ehost)->render_view_host() ) I still wish that rather than iterating profile managers' extension process managers, I could determine the ExtensionHost directly from the RenderViewHost, and this whole fix would be a simple one liner. But an ExtensionHost creates the RenderViewHost and Extension members. The likely design is that the RenderViewHost should not know about the ExtensionHost, therefore iterating ExtensionHosts mat be the only way... -- 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 -~----------~----~----~----~------~----~------~--~---
