A memory leak happens when a program doesn't release memory after it has accessed it. It's not uncommon for me to have FireFox running with over 100,000KB of memory accessed in the task manager.ducke said:SLEEPY GIANT ~ > memory leak ??? What is that ??? yesterday when I was looking into it " FF " a lot of peeps said the same thing ?
I would like to try it out on my getto laptop " Armada 7800 " does it need a lot space cause it does not have much
- http://developers.slashdot.org/article.pl?sid=06/02/14/2154224&from=rssThe Firefox memory leak is not a bug. It's a feature! The 'feature' is how the pages are cached in a tabbed environment." From the article: "To improve performance when navigating (studies show that 39% of all page navigations are renavigations to pages visited less than 10 pages ago, usually using the back button), Firefox 1.5 implements a Back-Forward cache that retains the rendered document for the last five session history entries for each tab. This is a lot of data. If you have a lot of tabs, Firefox's memory usage can climb dramatically. It's a trade-off. What you get out of it is faster performance as you navigate the web."