Firefox running even closed...

English Applications
1

Hi there!

Dunno if it is a bug or what but if I close firefox always stay consuming 50% **CPU **according system monitor…

let me few seconds to shutdown ff and take an image!

well…didn’t happen this time…

2

goro goren wrote:
> Hi there!
>
> Dunno if it is a bug or what but if I close firefox always stay
> consuming 50% *CPU *according system monitor…
>
> let me few seconds to shutdown ff and take
Start firefox from terminal/konsole using command and check whether the
problem occurs

firefox -safe-mode

–
GNOME 3.10.2
openSUSE 13.1 (Bottle) (x86_64) 64-bit
Kernel Linux 3.11.6-4-desktop

3

happened a minute ago:

http://s28.postimg.org/7xuvr9955/snapshot4.jpg](http://postimg.org/image/7xuvr9955/)

>:(:yawn::emoMAD:

4

I am seeing that occasionally with firefox 26, and perhaps it happened with firefox 25. I don’t recall it before then.

It is still rather rare, less than one time in 10. But it does happen.

5

It is probably looping on something, perhaps some bad javascript.

I use “noscript”, which might be why I don’t see this as often.

6

On Mon, 13 Jan 2014 20:16:01 GMT
goro goren <goro_goren@no-mx.forums.opensuse.org> wrote:

>
> Hi there!
>
> Dunno if it is a bug or what but if I close firefox always stay
> consuming 50% *CPU *according system monitor…
>
> let me few seconds to shutdown ff and take an image!
>

How did you close FF? I ask because I’ve seen several complaints that
an application didn’t close down when they clicked the ‘x’ button
which, of course, it wouldn’t do.

–
Graham P Davis, Bracknell, Berks.
openSUSE 13.1 (64-bit); KDE 4.12.0; AMD Phenom II X2 550 Processor;
Kernel: 3.12.7; Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306

7

Over the many, many years FF has had a spotty record shutting down properly. I’ve seen memory leaks (ie running FF for a long time exhausts resources so your machine runs more and more slowly).

In the early years I’d attributed it to sloppy internal coding but nowadays the cause may be more complex. One of the reasons I use FF over other faster browsers is because FF supports so many plugins and if the plugins are coded poorly, then I’d assume they could cause FF not to shut down properly.

So, unless and until a tool is written to analyze FF internally (which AFAIK doesn’t exist), FF will probably always have periodic problems.

TSU

8

This could tell some?:

http://s21.postimg.org/td51wa6n7/snapshot6.jpg](http://postimg.org/image/td51wa6n7/)

9

Occasionally it happens to me too.
I discovered or more accurately I suspect Flash player to cause it.
It usually happens when I watch something and then close.
I do not suspect Java, because I have it disabled.

Why? No idea…