Comment #21 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
Ok, I take it back (my bad). By poking around in the continuous build directories I can pretty much figure out that Gentoo binary releases appear to be tracking about a day or two behind the builds @ build.chromium.org. I can't quite figure out why there doesn't appear to be a 32167 release (the Gentoo current release) but there are before and after releases. The REVISION in the LATEST directory also has the version number. So I'll test that next time I restart chrome. But given the XPCOM errors I don't expect it to fix the problem. I might suggest that the XPCOM error be made a little more informative using the strerror function and some indication of the system call which is failing. Also, since all of the defunct processes are children of the master parent process one could try waiting, waitpid(-1, &status, WNOHANG) or something similar before issuing any fork() calls. Or something similar perhaps every 5-10 fork() calls (I'm not sure about clone() calls) so one isn't consuming CPU needlessly but is also minimizing the number of defunct processes that can accumulate. -- 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
