| 1 |
On Sun, Nov 10, 2013 at 04:07:34PM -0600, Dale wrote: |
| 2 |
|
| 3 |
> >> I have noticed something that really bugs me. I sometimes have a few |
| 4 |
> >> Firefox sessions running. I do this because I have to be logged into a |
| 5 |
> >> website with more than one user/password. Here is my issue. If I click |
| 6 |
> >> the X box to close a session of Firefox, it doesn't seem to kill the |
| 7 |
> >> process. [...] |
| 8 |
|
| 9 |
> > What version of Firefox? What addons (if any) do you use with Firefox? |
| 10 |
|
| 11 |
> Oh good heavens. I have lots of add ons installed. It would take me a |
| 12 |
> while to list them all, heck, just to get a list much list post them |
| 13 |
> here. |
| 14 |
|
| 15 |
There’s an addon for that. ;-) |
| 16 |
But if you start like that, I would recommend to thin out the list. You |
| 17 |
never know what kind of conflicts and other interactions there might be |
| 18 |
between addons. We could discuss this in another thread. ;-) |
| 19 |
|
| 20 |
> lol I recall abduction, tab utilities, last pass off the top of |
| 21 |
> my head. However, I have a test session that has very very few add ons |
| 22 |
> and it does the same way. |
| 23 |
|
| 24 |
With session you mean firefox profile? I know of no other way of having |
| 25 |
different sets of addons simultaneously (short of Walter’s idea of using |
| 26 |
different unix users). |
| 27 |
|
| 28 |
> Also, I run into this with other processes as well. It seems to me |
| 29 |
> that some package or the kernel is not killing processes as it should. |
| 30 |
> I just don't know what that is. |
| 31 |
|
| 32 |
What processes? If it’s Seamonkey which you mentioned elsewhere, it may |
| 33 |
be the same problem/cause. |
| 34 |
You could possibly identify the perpetrating process by looking at its |
| 35 |
memory footprint. A process that is close to terminating would use much |
| 36 |
less memory than a fully running process with tabs. |
| 37 |
|
| 38 |
> It could even be a KDE bug. |
| 39 |
|
| 40 |
I don’t really think so. You click the X, the window manager notifies |
| 41 |
the program in the window to quit. The program destroys its X client, |
| 42 |
KWin processes that event and poof. Nothing more KDE can do (IMHO). |
| 43 |
|
| 44 |
> I know when I go to boot runlevel, I have to kill quite a few |
| 45 |
> processes that are pretty stubborn to kill. kill -15 usually doesn't |
| 46 |
> work so I end up using -9 to get it to die. |
| 47 |
|
| 48 |
If you go to *that* length (switch to boot and kill processes manually), |
| 49 |
why not do the *cough* Ubuntu way and simply reboot, since killing X |
| 50 |
means killing most of your environment of running applications anyway? |
| 51 |
-- |
| 52 |
Gruß | Greetings | Qapla’ |
| 53 |
Please do not share anything from, with or about me with any Facebook service. |
| 54 |
|
| 55 |
The total intelligence on a planet is constant. Population grows... |
Archives