Comment #16 on issue 23778 by Robert.Bradbury: Chrome fails to collect defunct/zombie processes remaining from closed tabs/windows. http://code.google.com/p/chromium/issues/detail?id=23778
My current chrome has crept up from ~35 to ~63 defunct processes. I am fairly sure that I have not started/exited 30 windows/tabs in 6 hours -- indeed during much of that time chrome was completely idle -- so I'd point the finger at background processes started by javascript or flash (potentially pointing out security holes in both of them). I have looked at the URL provided and it is great that you are providing the LATEST continuous builds. But the fact that you are distributing it in a ".zip" format indicates to me that you are still operating with a MS Windows mindset and not a Linux mindset [1] (which would dictate a .Z, .gz or .bz2 formats). And yes I could take the time to download it and run chrome using it but that would require closing my current session and restarting it. Since my last "large" restart (after an upgrade of the Gentoo binary version failed to reopen all of the windows/tabs) failed completely I am reluctant to do that. I presume that due to the process model upgrading the installed chromium while running chromium is problematic. I would stress that I can/will go look at updated source code *if* you indicate to me in this bug thread precisely *which* source files issue fork()s and which issue wait/waitpids(). Until then, given my experience with firefox problems, I'll assume chrome is (once again) MS-Windows centric and tends to treat Linux as an afterthought. 1. Though I can and have used Windows off and on for ~10 years I have used Unix/Linux for ~35 years and still prefer it because I can actually go read the source code when problems like this appear. -- 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
