Updates:
Status: WontFix
Comment #1 on issue 6671 by [email protected]: possibly memory leak in dev
chrome release 2.0.175.2
http://code.google.com/p/chromium/issues/detail?id=6671
I have no idea what the data above means.
Two tabs can live in the same process, especially if one tab opens another
tab using
javascript (window.open()). GMail does this, for example, so it's pretty
common to
see several tabs opened from links in GMail living in the same process.
It looks like the data above is from about:memory, tracking the same
process id
(5132). The process never gets closed, so the memory doesn't get freed.
If you did have a new process, they can't share memory. You'd also see the
process ID
change (each new process gets a unique id from Windows) on the about:memory
page.
Maybe you were opening tabs from links on the '0 in WW-WIRELESS
WW-WIRELESS-REL'
page.
--
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
-~----------~----~----~----~------~----~------~--~---
