You are not logged in.
Sometimes I find that pkill chromium doesn't clean up all the stay behinds. I need two rounds of pkill to get them all.
Maybe try this one:
#!/bin/bash
chromium
me=$(basename $0)
if [[ -z $(wmctrl -l | grep Chromium) ]]; then
processes=$(ps ax | grep chromium | grep -v grep | grep -v $me | awk '{print $1}')
if [[ $processes == "" ]]; then
echo -e "\e[1;32mChromium exited cleanly, no processes to kill.\e[0m"
else
echo -e "\e[1;31mChromium left zombie processes, cleaning up...\e[0m"
kill $processes
fi
else
echo -e "\e[1;32mThere are still Chromium windows open. Not cleaning up yet.\e[0m"
fi
Offline
I can confirm the bug with Chrome 25.0.1364.172 and nvidia 313.26.
Offline
I think I am experiencing this issue with KDE 4.10 and the Intel gfx driver. Running Chromium 26.0.1410.43 (189671)
https://bbs.archlinux.org/viewtopic.php … 6#p1253126
Last edited by ayr0 (2013-04-02 17:05:08)
Offline
Sorry, is the problem maybe solved finally?
Offline
No, it's still not solved.
Chromium: Version 26.0.1410.43 (189671)
extra/nvidia 313.30-2 [installed]
extra/nvidia-libgl 313.30-2 [installed]
extra/nvidia-utils 313.30-2 [installed]
multilib/lib32-nvidia-libgl 313.30-1 [installed]
multilib/lib32-nvidia-utils 313.30-1 [installed]
Personal spot :: https://www.smirky.net/ :: Try not to get lost!
Offline
I thought it was with the latest NVIDIA driver that just came out, but I still occasionally run into this as well.
Offline
Offline
As far as I know, the Chromium package provided through pacman is compiled from now on (or until NVIDIA cleans it's mess) without tcmalloc. I haven't seen any zombie processes since then so I encourage you all to update
Personal spot :: https://www.smirky.net/ :: Try not to get lost!
Offline
As far as I know, the Chromium package provided through pacman is compiled from now on (or until NVIDIA cleans it's mess) without tcmalloc. I haven't seen any zombie processes since then so I encourage you all to update
Great, i'm dropping google-chrome in favour to chromium. Thanks for posting!
Offline
It seems as though someone changed the chromium package at chromium 26.0.1410.43-3
+ -Dlinux_use_tcmalloc=0 \
so perhaps this problem has gone away. Unfortunately I switched to using nouveau in the mean time. I noticed some minor issues like not being able to show the gpu temperature, but nothing too strange. I do see occasional lock ups in my time wasting with swell foop. Not sure whether I'll switch back.
Offline
I noticed some minor issues like not being able to show the gpu temperature
Shameless self promotion
https://aur.archlinux.org/packages.php?ID=52645
https://bbs.archlinux.org/viewtopic.php?id=127070
(if you have NV50 card)
Last edited by karabaja4 (2013-04-13 22:38:00)
Offline
Seems solved on chrome, testing needed
https://code.google.com/p/chromium/issu … 177218#c14
#14 phajdan.jr@chromium.org
nvidia-drivers-331.20 claims to fix this issue:"Fixed a bug that could cause a deadlock when forking from OpenGL programs which use some malloc implementations, such as TCMalloc."
I'd appreciate some tests with that - please report results.
#15 dvpdiner2
Based on a few days with the new nVidia drivers, I haven't seen any Chrome_ProcessL processes recently.
Offline