From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Firefox not killing processes on close
Date: Mon, 11 Nov 2013 23:40:28 +0100 [thread overview]
Message-ID: <20131111224028.GA17644@nukleus.lan> (raw)
In-Reply-To: <528003A6.1040405@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2539 bytes --]
On Sun, Nov 10, 2013 at 04:07:34PM -0600, Dale wrote:
> >> I have noticed something that really bugs me. I sometimes have a few
> >> Firefox sessions running. I do this because I have to be logged into a
> >> website with more than one user/password. Here is my issue. If I click
> >> the X box to close a session of Firefox, it doesn't seem to kill the
> >> process. [...]
> > What version of Firefox? What addons (if any) do you use with Firefox?
> Oh good heavens. I have lots of add ons installed. It would take me a
> while to list them all, heck, just to get a list much list post them
> here.
There’s an addon for that. ;-)
But if you start like that, I would recommend to thin out the list. You
never know what kind of conflicts and other interactions there might be
between addons. We could discuss this in another thread. ;-)
> lol I recall abduction, tab utilities, last pass off the top of
> my head. However, I have a test session that has very very few add ons
> and it does the same way.
With session you mean firefox profile? I know of no other way of having
different sets of addons simultaneously (short of Walter’s idea of using
different unix users).
> Also, I run into this with other processes as well. It seems to me
> that some package or the kernel is not killing processes as it should.
> I just don't know what that is.
What processes? If it’s Seamonkey which you mentioned elsewhere, it may
be the same problem/cause.
You could possibly identify the perpetrating process by looking at its
memory footprint. A process that is close to terminating would use much
less memory than a fully running process with tabs.
> It could even be a KDE bug.
I don’t really think so. You click the X, the window manager notifies
the program in the window to quit. The program destroys its X client,
KWin processes that event and poof. Nothing more KDE can do (IMHO).
> I know when I go to boot runlevel, I have to kill quite a few
> processes that are pretty stubborn to kill. kill -15 usually doesn't
> work so I end up using -9 to get it to die.
If you go to *that* length (switch to boot and kill processes manually),
why not do the *cough* Ubuntu way and simply reboot, since killing X
means killing most of your environment of running applications anyway?
--
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me with any Facebook service.
The total intelligence on a planet is constant. Population grows...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-11-11 22:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 21:38 [gentoo-user] Firefox not killing processes on close Dale
2013-11-10 21:53 ` staticsafe
2013-11-10 22:07 ` Dale
2013-11-11 22:40 ` Frank Steinmetzger [this message]
2013-11-11 22:49 ` Peter Weilbacher
2013-11-12 2:28 ` Dale
2013-11-11 1:07 ` Walter Dnes
2013-11-11 3:53 ` Dale
2013-11-11 6:36 ` Alan McKinnon
2013-11-11 7:39 ` Dale
2013-11-11 11:18 ` Alan McKinnon
2013-11-12 1:13 ` Dale
2013-11-11 14:35 ` gottlieb
2013-11-11 14:58 ` Neil Bothwick
2013-11-11 6:24 ` Yohan Pereira
2013-11-11 7:44 ` Dale
2013-11-11 7:53 ` Yohan Pereira
2013-11-11 8:19 ` Dale
2013-11-22 12:47 ` Dale
2013-11-11 14:52 ` Bruce Hill
2013-11-11 17:13 ` Alexander Kapshuk
2013-11-11 10:11 ` Neil Bothwick
2013-11-11 18:28 ` Edward M
2013-11-11 18:50 ` Bruce Hill
2013-11-11 19:44 ` Edward M
2013-11-11 19:57 ` Alexander Kapshuk
2013-11-11 20:46 ` Edward M
2013-11-11 20:49 ` Alexander Kapshuk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131111224028.GA17644@nukleus.lan \
--to=warp_7@gmx.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox