«

Just read in the Mozillazine that Firefox can drain memory.

How?

Why?

Can it be prevented?

Can I check to see if that's happening to my machine?


rgds/Bob

Le 03/04/2005 14:18, BobW a écrit :
> Just read in the Mozillazine that Firefox can drain memory.
>
> How?
>
> Why?
>
> Can it be prevented?
>
> Can I check to see if that's happening to my machine?
>
>
> rgds/Bob
>
>
>
>
>

Fixed with the 1.0.2 version

--
Utilisez le butineur, le courriéleur et le lecteur de nouvelles
.... avec lequel vous vous sentez le plus sécurisé

> > Just read in the Mozillazine that Firefox can drain memory.
> >
> > How?
> >
> > Why?
> >
> > Can it be prevented?
> >
> > Can I check to see if that's happening to my machine?
> >
> >
> > rgds/Bob
> >
>
> Fixed with the 1.0.2 version
>
> --
> Utilisez le butineur, le courriéleur et le lecteur de nouvelles
> ... avec lequel vous vous sentez le plus sécurisé

I wonder, cause on my system 1.0.2 is slowing down things much more then
earlier version.

--
Menno
=====================
My 3D Art can be seen on
http://www.3dart4u.com
=====================
Remove nopam in mail address when mailing me

Michel Doucet wrote:
> Le 03/04/2005 14:18, BobW a écrit :
> > Just read in the Mozillazine that Firefox can drain memory.
> >
> > How?
> >
> > Why?
> >
> > Can it be prevented?
> >
> > Can I check to see if that's happening to my machine?
> >
>
> Fixed with the 1.0.2 version
>

I don't know where you got that information -- 1.0.2 was a minor
security update. There are *plenty* of people who still have memory
leak problems, and would disagree with your statement. Luckily, I am
not one of those individuals

There have been memory "bugs" for as long as I can remember.

Firefox "Memory Leak" Bugs: [http://tinyurl.com/6el6w]

--
Brian

I thought as much. I'm seeing memory drains for the first time here
since I started using Firefox. They started with 1.0.2. Maybe it just
took longer with 1 GB memory, maybe not.

The system hesitates when I type sometimes.


> Michel Doucet wrote:
>
>>Le 03/04/2005 14:18, BobW a écrit :
>>
>>>Just read in the Mozillazine that Firefox can drain memory.
>>>
>>>How?
>>>
>>>Why?
>>>
>>>Can it be prevented?
>>>
>>>Can I check to see if that's happening to my machine?
>>>
>>
>>Fixed with the 1.0.2 version
>>
>
>
> I don't know where you got that information -- 1.0.2 was a minor
> security update. There are *plenty* of people who still have memory
> leak problems, and would disagree with your statement. Luckily, I am
> not one of those individuals
>
> There have been memory "bugs" for as long as I can remember.
>
> Firefox "Memory Leak" Bugs: [http://tinyurl.com/6el6w]
>

BobW wrote:
> Just read in the Mozillazine that Firefox can drain memory.
>
> How?


It doesn't flush pages you've visited and then closed from RAM, the way
I understand it.

On my machine, XP with 512 megs RAM, Firefox usage eventually bloats up
to 300 megs and beyond, even with only one page currently open. I've
tried the tweaks suggested in many places, but they don't fix the
problem. Sometimes it takes a long time (over a day) to bog down the
system, sometimes it happens pretty fast. Occasionally Firefox will hog
99% of CPU cycles for no reason I can figure out, but that dosn't happen
to me often.

I think fixing this RAM/CPU issue should be the number one priority of
Firefox developers, beyond security and everything else.

Firefox is still my favorite browser. When it goes nuts, I stop the
program and restart it.

""f®@nK panu©©I"" <> wrote in message
news:s9f4e.3576$%b1.3329@trnddc08...
> BobW wrote:
>> Just read in the Mozillazine that Firefox can drain memory.
>>
>> How?
>
>
> It doesn't flush pages you've visited and then closed from RAM, the way I
> understand it.
>
> On my machine, XP with 512 megs RAM, Firefox usage eventually bloats up to
> 300 megs and beyond, even with only one page currently open. I've tried
> the tweaks suggested in many places, but they don't fix the problem.
> Sometimes it takes a long time (over a day) to bog down the system,
> sometimes it happens pretty fast. Occasionally Firefox will hog 99% of
> CPU cycles for no reason I can figure out, but that dosn't happen to me
> often.
>
> I think fixing this RAM/CPU issue should be the number one priority of
> Firefox developers, beyond security and everything else.
>
> Firefox is still my favorite browser. When it goes nuts, I stop the
> program and restart it.

So, if I get it - when the computer slows that's an indication of drained
memory and to get that memory back I should close Firefox, then reopen it??

Thanks/Bob

BobW wrote:

> So, if I get it - when the computer slows that's an indication of drained
> memory and to get that memory back I should close Firefox, then reopen it??


Works for me. You may want to verify with Task Manager that it's
Firefox that's causing the problem before you shut it down. Sometimes
some other program such as emule will eat your resources.

type about:config into the location bar, press enter, right click any
line, choose "new">"integer", paste this into the dialogue that appears:

browser.cache.memory.capacity

click okay, specify 16000 in the next dialogue that appears, restart
firefox.


BobW wrote:
> Just read in the Mozillazine that Firefox can drain memory.
>
> How?
>
> Why?
>
> Can it be prevented?
>
> Can I check to see if that's happening to my machine?
>
>
> rgds/Bob
>
>
>
>
>

----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

Scott K. wrote:
> type about:config into the location bar, press enter, right click any
> line, choose "new">"integer", paste this into the dialogue that appears:
> browser.cache.memory.capacity
> click okay, specify 16000 in the next dialogue that appears, restart firefox.


Already did that, but thanks. Doing a search for this issue yields up
quite a large amount of users who have this problem with Firefox. It's
not a deal-killer for me - I'll stick with this browser because I like
it - but it's a big problem that I think should be top priority for the
developers.