Anyone else noticed Chrome leaving processes behind after updating to version 35?
Code:
gazl@ws1:/opt/google/chrome$ ps xjf
PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND
7314 7344 7344 7344 ? -1 Ss 1000 0:00 /usr/bin/dwm
7344 7386 7386 7386 ? -1 SNsl 1000 0:03 \_ /opt/firefox/firefox
7344 7448 7448 7448 ? -1 SNs 1000 0:00 \_ xterm
7448 7450 7450 7450 pts/0 7783 SNs 1000 0:00 \_ bash
7450 7456 7456 7450 pts/0 7783 SNl 1000 0:01 \_ /opt/google/chrome/chrome
7456 7461 7456 7450 pts/0 7783 SN 1000 0:00 | \_ /opt/google/chrome/chrome --type=sandbox-ipc
7456 7462 7456 7450 pts/0 7783 SN 1000 0:00 | \_ /opt/google/chrome/chrome --type=zygote
7462 7466 7456 7450 pts/0 7783 SN 1000 0:00 | | \_ /opt/google/chrome/nacl_helper
7456 7484 7456 7450 pts/0 7783 SN 1000 0:00 | \_ /opt/google/chrome/chrome
7450 7671 7671 7450 pts/0 7783 SNl 1000 0:00 \_ /opt/google/chrome/chrome
7671 7676 7671 7450 pts/0 7783 SN 1000 0:00 | \_ /opt/google/chrome/chrome --type=sandbox-ipc
7671 7677 7671 7450 pts/0 7783 SN 1000 0:00 | \_ /opt/google/chrome/chrome --type=zygote
7677 7681 7671 7450 pts/0 7783 SN 1000 0:00 | | \_ /opt/google/chrome/nacl_helper
7671 7699 7671 7450 pts/0 7783 SN 1000 0:00 | \_ /opt/google/chrome/chrome
7450 7783 7783 7450 pts/0 7783 RN+ 1000 0:00 \_ ps xjf
1 7432 7384 7384 ? -1 S 1000 0:00 /usr/libexec/gconfd-2
1 7408 7384 7384 ? -1 Sl 1000 0:00 /usr/libexec/gvfsd
1 7402 7384 7384 ? -1 Sl 1000 0:00 /usr/libexec/at-spi-bus-launcher
1 7384 7384 7384 ? -1 Ss 1000 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
1 7383 7344 7344 ? -1 S 1000 0:00 dbus-launch --sh-syntax --exit-with-session
In the case above both instances of chrome were started/exited sequentially and have been exited, and before anyone asks I don't have the "allow background jobs to continue" option set in its settings (not that it should be running any background jobs), so its not that.
Doesn't seem to matter if it's backgrounded or not when you start it from the terminal, but if you don't background them you end up having to ctrl-c and that results in zombies and then causes a subsequent invocation of chrome to hang completely on start-up, so it only makes matters worse. Turning off hardware acceleration doesn't seem to make any difference either.
It also seems to be a bit hit and miss, as some times it does end cleanly, but more often than not I'm finding it doesn't.
P.S. This is on Slackware64 14.1, none multilib and with chrome 35.0.1916.114, built from Pat's slackbuild script from extras (minus the sed which doesn't seem to be needed these days)
P.P.S. Also tried removing ~/.cache/google-chrome and ~/.config/google-chrome.
P.P.P.S Forgot to mention, I get a
Code:
[7943:7943:0525/150443:ERROR:component_loader.cc(138)] Failed to parse extension manifest.
when it's started, but it doesn't seem to be fatal.