Comment #48 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
After some further research on this problem, it seems to come down to how the plugins directory is setup in general. Some of the various Gentoo setups seemed to link the chromium-browser plugins directory to the Mozilla/netscape plugins directory (/usr/lib/nsbrowser/plugins) which contains several plugins which may not play nicely with Chromium. In particular I think it is the plugin "mozplugger.so" which may be the culprit responsible for creating the zombie processes. Once I setup the plugins directory for chromium myself (so it only contains symlinks to javaplugin.so, libflashplayer.so and nppdf.so) the problem stopped occurring. So I think strictly speaking this is not a chromium bug so much as a distribution/setup bug. Though it could be resolved by chromium only activating "known to work" plugins. One could view the possible use of any plugin in the plugins directory to be a potential security hole. The issue with libflashplayer.so running amok (showing up consuming large amounts of CPU as the exe process) still does exist however -- and could be resolved by active management by chromium of the exe subprocess -- flash should be stopped by killing the "exe" process with a SIGSTOP when the windows are outside of the active terminal/workspace or all minimized and not restarted (SIGCONT) until the window becomes active again. So I would label this issue as quasi-resolved. -- 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
