Google Chrome (all versions in the tree) leaves stale processes on exit. Some of these processes can be killed with SIGTERM, but some can only be killed with SIGKILL ("kill -9"). Worse, the KDE desktop sometimes freezes when exiting Chrome and there are stale processes. Only the desktop, not application windows. Killing all processes makes the desktop respond again.
Created attachment 321124 [details] emerge --info google-chrome
$ emerge -pv google-chrome These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] www-client/google-chrome-21.0.1180.77_beta150576 USE="-plugins" LINGUAS="-am -ar -bg -bn -ca -cs -da -de -el -en_GB -es -es_LA -et -fa -fi -fil -fr -gu -he -hi -hr -hu -id -it -ja -kn -ko -lt -lv -ml -mr -ms -nb -nl -pl -pt_BR -pt_PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -vi -zh_CN -zh_TW" 0 kB
Stale processes after exiting Chrome: $ ps aux | grep chrome realnc 5099 0.0 0.0 301392 15100 ? S 19:00 0:00 /opt/google/chrome/chrome realnc 5100 0.0 0.0 6204 600 ? S 19:00 0:00 /opt/google/chrome/chrome-sandbox /opt/google/chrome/chrome --type=zygote realnc 5101 0.0 0.2 340060 40004 ? S 19:00 0:00 /opt/google/chrome/chrome --type=zygote realnc 5105 0.0 0.1 208236 24172 ? S 19:00 0:00 /opt/google/chrome/nacl_helper_bootstrap /opt/google/chrome/nacl_helper --at-zero --r_debug=0x0000000000213000 realnc 5106 0.0 0.0 364648 14540 ? S 19:00 0:00 /opt/google/chrome/chrome --type=zygote realnc 5145 0.0 0.2 695964 32880 ? S 19:00 0:00 /opt/google/chrome/chrome
Yeah, I've seen that myself. Do you use nvidia-drivers? I think this is bug 413637.
Yes, I'm on nvidia-drivers. Using chromium is not an option, unless it supports Chrome's Flash plugin (I switched from Firefox to Chrome because of Flash; www-plugins/adobe-flash doesn't work reliably anymore, while Google's Flash version works without issues.)
As Paweł indicates, please report the issue upstream if you want to see it fixed in google-chrome. You can use google-chrome's "pepper" flash plugin with chromium. Just put the following in /etc/chromium/default: CHROMIUM_FLAGS="--ppapi-flash-path=/opt/google/chrome/PepperFlash/libpepflashplayer.so"
Thank you very much! I will try Chromium instead. Yes, I reported the issue, both in the feedback dialog in Chrome itself, as well as on Google's bug tracker. But the issue there is two years old and Google doesn't seem to give a fsck :-P
Chromium works fine. Flash too, though I guess it would be better if there was a USE flag for this that installs the latest Flash from Chrome without the user needing to install Chrome too. It now just sits there. Same goes for the PDF plugin. I got it to work by symlinking "/opt/google/chrome/libpdf.so" to "/usr/lib64/chromium-browser/". I think these should be offered either by USE flags, or by default when the "bindist" USE flag is not set.
That's not going to happen. The google-chrome distfiles disappear without warning, so we really can't depend on them in a stable package like chromium. I might consider creating a package that would only install the plugins from google-chrome, if only to avoid pulling in all of google-chrome's RDEPENDS.
Yeah, that's what I meant actually. Download the Chrome *.deb that is the same version as Chromium and extract only the Flash and PDF plugins and put then in /usr/lib/chromium-browser(/PepperFlash).
The release notes for nvidia-drivers-331.20 claim to have fixed this problem: "Fixed a bug that could cause a deadlock when forking from OpenGL programs which use some malloc implementations, such as TCMalloc."
(In reply to David Klempner from comment #11) > The release notes for nvidia-drivers-331.20 claim to have fixed this problem: > > "Fixed a bug that could cause a deadlock when forking from OpenGL programs > which use some malloc implementations, such as TCMalloc." Thanks, please see my comment in https://bugs.gentoo.org/show_bug.cgi?id=413637#c31
