An urban myth dating back to pre-version 2.5 days. Any memory leaks in FF that a user would notice were solved by then. Memory issues nowadays are related to add-ons by 3rd parties.
I typically run with around 5 tabs and never close the browser for days on end. Memory usage is always between 200-300Mb for FF4.
Of all the friends/family/business users who rely on me for tech support, no one is any different than what I have. Now that's on Windows. I do not have FF4 on my FreeBSD boxes yet.
Memory usage: Several new technologies work together to reduce the amount of memory used by Firefox 3 over a web browsing session. Memory cycles are broken and collected by an automated cycle collector, a new memory allocator reduces fragmentation, hundreds of leaks have been fixed, and caching strategies have been tuned.
Mr ignorance, this is from FF official patch notes not from any module.
I'm not talking about extensions at all. If we count extensions - this is not hundreds of leaks -- it case "with modules" I don't know such big numbers (kidding).
If you want holy war about FF say please, I will leave then. But killasmurf86 started topic about 2GB memory consumption, not about your personal preferences/like/dislike (I use FF too under FreeBSD).
Last time I used Firefox (3.0.something, about two years ago) it was taking a GB of memory after a day of usage even without any third party addons or plugins installed...
What I said was leaks that the user would notice. A lot of programs, including FF, have leaks that don't hang around long enough to cause the problems people think they do. Those who have issues of gigabytes of ram being taken up by FF are issues not caused by the browser.
Sure killasmurf86 uses many addons (normally I use 2 of them), so it just eating memory faster than usual =) I think it's no other way to debug - just disable them one by one.
Sure killasmurf86 uses many addons (normally i use 2 of them), so it just eating mem faster than usually =) I think its no other way to debug - just disable them 1by1
I find that every time I click within the web component windows in firefox, my hard drive churns a bit. This isn't ideal for my poor little hard drive.
Also, I had my suspicions that Firefox was memory leaking but didn't want to say anything until others noticed a similar issue.
I find that every time I click within the web component windows in firefox, my hard drive churns a bit. This isn't ideal for my poor little hard drive.
If the files it's trying to access are stored in the user profile, try moving the profile to a memory disk, if the memory size allows it of course. You can make a script that populates the appropriate directories every time before running the browser.
Again, not that you'd notice. It's been a while since I've looked at this issue so I dialed up Asa Dotzler to see if anything's different.
No. Nothing is different than what I said. Users won't notice memory leaks. All browsers have them (of course) but the only significant problem FF has is with GMail. I had heard of this some time ago. GMail does a lot of fancy stuff with javascript but I don't recall what the core of the problem Firefox has with it.
An urban myth dating back to pre-version 2.5 days. Any memory leaks in FF that a user would notice were solved by then. Memory issues nowadays are related to add-ons by 3rd parties.
Firefox, by design highly encourages usage of 3rd party add-ons/extensions.
Furthermore, firefox apparently allows these extensions to cause memory leaks.
Isn't it fair to say this is a problem with firefox itself?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
