From: Merciadri Luca on
Hi,

I noticed on many computers with Debian, whatever the kernel (2.6.xx, xx
>= 26), that, once ``too much'' tabs have been opened, Firefox/Iceweasel
becomes sluggish, slower and slower, and often stalls after some time. I
also noticed that, when becoming more and more sluggish, it takes more
and more RAM, even when all the pages are completely loaded. Why? Am I
the only person who's experiencing this? Is there an objective
explanation to this?

--
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
I use PGP. If there is an incompatibility problem with your mail
client, please contact me.


No man is rich enough to buy back his past. (Oscar Wilde)

From: Camaleón on
On Fri, 07 May 2010 19:58:26 +0200, Merciadri Luca wrote:

> I noticed on many computers with Debian, whatever the kernel (2.6.xx, xx
>>= 26), that, once ``too much'' tabs have been opened, Firefox/Iceweasel
> becomes sluggish, slower and slower, and often stalls after some time. I
> also noticed that, when becoming more and more sluggish, it takes more
> and more RAM, even when all the pages are completely loaded. Why? Am I
> the only person who's experiencing this? Is there an objective
> explanation to this?

He... did you never search in Google for "Firefox memory hog"? O:-)

There's even a Mozilla KB explaining the issue:

Reducing memory usage - Firefox
http://kb.mozillazine.org/Memory_Leak

Also, never versions (>3.5.x) provide /a bit/ better memory management.

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/pan.2010.05.07.18.17.57(a)gmail.com
From: Kelly Clowers on
On Fri, May 7, 2010 at 10:58, Merciadri Luca
<Luca.Merciadri(a)student.ulg.ac.be> wrote:
> Hi,
>
> I noticed on many computers with Debian, whatever the kernel (2.6.xx, xx
>>= 26), that, once ``too much'' tabs have been opened, Firefox/Iceweasel
> becomes sluggish, slower and slower, and often stalls after some time. I
> also noticed that, when becoming more and more sluggish, it takes more
> and more RAM, even when all the pages are completely loaded. Why? Am I
> the only person who's experiencing this? Is there an objective
> explanation to this?

I dunno. I myself have never had serious memory problems with Mozilla
or Firefox. In old versions of Mozilla (~0.9-1.7) and FF 1 and 2 there where
definite limits to how many tabs I could open without crashing. With current
versions, though, I can run over a hundred tabs with no problem. I am
currently at ~1,250MB resident for SeaMonkey, but this doesn't seem
unreasonable for how many tabs there are. It certainly doesn't grow over
time (this instance has probably been running for 3 days or more), only
with new tabs, or larger pages loaded into tabs.

So many people report these problems, and they are clearly real, but I
wonder why I have never had them, with different hardware (AMD and
Intel), and different OSs (2K, XP, 7, and several version of Debian).

Sorry, no real help, just my experiences.

* note: I use the nightlies from Mozilla, rather than Iceweasel/Iceape.


Cheers,
Kelly Clowers


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/y2w1840f6971005071827o36b23598s54a0d9e157925ce9(a)mail.gmail.com
From: Merciadri Luca on
Kelly Clowers wrote:
> I dunno. I myself have never had serious memory problems with Mozilla
> or Firefox. In old versions of Mozilla (~0.9-1.7) and FF 1 and 2 there where
> definite limits to how many tabs I could open without crashing. With current
> versions, though, I can run over a hundred tabs with no problem. I am
> currently at ~1,250MB resident for SeaMonkey, but this doesn't seem
> unreasonable for how many tabs there are. It certainly doesn't grow over
> time (this instance has probably been running for 3 days or more), only
> with new tabs, or larger pages loaded into tabs.
>
> So many people report these problems, and they are clearly real, but I
> wonder why I have never had them, with different hardware (AMD and
> Intel), and different OSs (2K, XP, 7, and several version of Debian).
>
> Sorry, no real help, just my experiences.
>
> * note: I use the nightlies from Mozilla, rather than Iceweasel/Iceape.
>
Thanks. But you specified that when dealing with tabs containing large
pages, the browser does not behave as if they were containing light
pages, didn't you? That's the problem.

--
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
I use PGP. If there is an incompatibility problem with your mail
client, please contact me.


It takes two to tango.

From: Girish Kulkarni on
On Fri, 07 May 2010 19:58:26 +0200 Merciadri Luca wrote:
> I noticed on many computers with Debian, whatever the kernel
> (2.6.xx, xx >= 26), that, once ``too much'' tabs have been opened,
> Firefox/Iceweasel becomes sluggish, slower and slower, and often
> stalls after some time. I also noticed that, when becoming more and
> more sluggish, it takes more and more RAM, even when all the pages
> are completely loaded. Why? Am I the only person who's experiencing
> this? Is there an objective explanation to this?

I'd had similar problem with Iceweasel on Lenny when my browser cache
limit was set to a large value. But things are okay after bringing it
down (to 20MB). You might want to try that.

Large cache slows Iceweasel down because it uses these large databases
of stored history to suggest addresses in each tab's address bar. I
also had a Zotero database, which used to worsen things.

Girish.

--
Girish Kulkarni - Allahabad, India - http://athene.org.in/girish


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100508180204.6d9ce52d(a)marvin.dhcp.hri