Comment #13 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
I don't know what it is either. I just tested printing in addition to windows and tabs and that isn't it. But the command: ps -deaf|grep "chrome.*defunct"| wc -l will give you the defunct process count and I currently have 35. I've got the chromium source (somewhat older) downloaded and if someone tells me where to go looking for the problem (I've dealt with the firefox source and the problem is not diagnosing or fixing things but knowing where to look). If I had a debugable version of chromium (gentoo only distributes a binary), I'd point it at the debugable GlibC libraries (on my system I run on non-debugable versions and debugable versions to debug firefox core-dumps) and set breakpoints in gdb in the source after any fork() calls to print the stack and the child process id's (which are presumably kept and fed to the task manager). Then wait for any child defunct processes to accumulate and see where/why the parent process went wrong. Unfortunately Gentoo (and most Linux distributions) do not distribute really debugable binaries so you have to compile them from source and I'm reluctant to do that with chrome given its seemingly fast release schedule (which is good for the user but bad from a perspective of user-to-debug-cycle contributions). -- 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
