Status: Unconfirmed Owner: ---- Labels: OS-Linux Area-Misc Size-Medium Type-Bug
New 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 Chrome Version : chromium-bin-4.0.219.4_p27359 (Gentoo ebuild version) OS + version : 2.6.31-gentoo CPU architecture (32-bit / 64-bit): 32 window manager : X.Org X Server 1.6.3.901 (1.6.4 RC 1) Release Date: 2009- 8-25 URLs (if applicable) : many Behavior in Firefox 3.x (if applicable): N/A Behavior in Chrome for Windows (optional): N/A? What steps will reproduce the problem? 1. Open many tabs/windows. 2. Close many tabs/windows. 3. Do a "ps f -C chrome"; note accumulation of may "defunct" processes. What is the expected result? Defunct processes should be collected, presumably by waitpid(2), by the parent whenever a window or tab is closed and a process exits. This avoids hitting the per-user-process limit or the system process limit. Care should be taken to avoid calling waitpid() when there are no processes to collect (which consumes CPU time wastefully). This tends to be a "showstopper" bug as the only way around the problem is to kill the chrome master process, force the exiting and collection of all chrome sub-processes and restart the chrome session. Restarting the large sessions I tend to run (50-100 windows, 500-800 tabs) can be exceedingly time consuming (10-20 maxed CPU minutes and 5-15 minutes maxed DSL bandwidth) and I will tend to avoid such "opportunities" if at all possible (read "stay with Firefox" for now). What happens instead? Defunct processes accumulate and eventually the user process limit (ulimit -u) is reached causing fork()s to fail and make general system use difficult to impossible. It may cause chrome to fail in strange ways (hanging on tab/window creations). Please provide any additional information below. Attach a screenshot and backtrace if possible. Attachments: ps.defunct 3.0 KB -- 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 -~----------~----~----~----~------~----~------~--~---
