Post by Adam Post by Adam Post by Paul Post by Adam
COMMAND %MEM RSS
nautilus 23.5 1867636
NetworkManager 7.4 594380
wpa_supplicant 6.1 490664
thunderbird 4.9 390432
unity-panel-ser 0.5 45048
This is after closing Nautilus. Why ?
Is Nautilus supposed to be running when you're
not using it ?
Not behaviour I expect.
Post by Paul
Did you start a file search, then dismiss the window ?
Don't remember. Possibly.
Post by Paul
Perhaps the process is a windowless runaway.
If so, not good.
Post by Paul
I vaguely remember mention of some file manager
being naughty, if you start a file search, then
close the window. The parent process might then live
on, when it's not supposed to.
Is it safe to kill the process ?
242 sudo apt-get install gnome-shell
253 sudo apt-get install vim-gnome
271 sudo apt-get install gnome-volume-control
Could any of this be related ? I know gnome-shell has memory leak issues.
But, I don't see gnome-shell in the ps list. Synaptic lists gdm package to
be removed along with gnome-shell. What functionality would I break ?
It doesn't look like gnome-shell is being used.
When something runs off with your memory, you have
a number of choices.
1) Find the command that requests that all applications
"shed weight". Not appropriate in this case, as there's
no evidence this zombie is "working for us".
2) Use "kill -9 <PIDvalue>" to kill the process.
The 9 is a signal. The 9 can't be intercepted.
"It's hammer time" so to speak. You can use sudo
for things owned by root. There are also
signal values which are "more polite" and allow
a process to put away its toys first.
3) Or, use reboot to stop it that way.
I didn't see nautilus running as a backgrounder
here, so assume yours is a rogue/zombie/runaway etc.
It's unlikely to have command line parameters passed
to it. I do that sometimes, but not that often. Most
people would launch Nautilus by clicking an icon in
The latter format is for cases where a redesign of
a file manager, leaves it with no onscreen space
to enter a URI. Neither of these is noteworthy in
the current situation.
I'm not going to contemplate the killing of random
things in your DE for sport :-) Let's just stick
with the current target.
SIGKILL 9 "Blammo!"
"The signals SIGKILL and SIGSTOP cannot be caught,
blocked, or ignored."
That's for cases where a process does not respond when
we ask nicely. You need a signal flavor in that case,
which returns control to the user.
"If no signal is specified, the TERM signal is sent."
And that's the polite knock on the door, and troublemakers
will ignore that.
sudo kill <PIDvalue> # "Knock, knock, Avon calling"
# SIGTERM can be intercepted.
True zombies, the zombie state is an intermediate state,
never intended for users to see. Yet, in the past, in
*all* OSes, they have manifested (I've seen the zombie state
in Windows). They also can't be killed, because... they're
in the process of dying, and the chance to kick them in
the nuts is over. A reboot will harvest technical zombies.
I also carelessly refer to "still living pests" as zombies,
to connote their unwillingness to listen to reason. But there
is actually a process state of "zombie" as well. And those
are in the netherworld, their resources half-harvested
perhaps. This is obviously a bug, but a carefully orchestrated
bug nonetheless. You can imagine as a server operator needing
24/7 service, you would not appreciate something like that.
(Server operators hate to reboot.)