Linked by lemur2 on Fri 15th Oct 2010 22:50 UTC
Mozilla & Gecko clones For its upcoming Firefox 4.0 release, Mozilla has been concentrating a great deal on what is often cited as the main shortcoming of Firefox ... its speed. For example, Firefox 4.0 will include GPU acceleration for both rendering and compositing on Windows 7/Vista, OSX and Linux, and it will have GPU acceleration for compositing only for Windows XP.
Thread beginning with comment 445269
To read all comments associated with this story, please click here.
memory leaks
by dayalsoap on Sat 16th Oct 2010 02:34 UTC
dayalsoap
Member since:
2010-05-19

How about the memory leak problems with FF? When I close some tabs, ideally, I'd like to see my RAM usage go down some. My FF on OSX consistently uses 600+MB ram.

Reply Score: 1

RE: memory leaks
by Quake on Sat 16th Oct 2010 02:36 in reply to "memory leaks"
Quake Member since:
2005-10-14

Me it's the opposite (Linux). I find Chrome to leak considerably to the point that my swap is in active use while Firefox's memory usage is considerably less.

Reply Parent Score: 1

RE[2]: memory leaks
by aliquis on Sat 16th Oct 2010 03:59 in reply to "RE: memory leaks"
aliquis Member since:
2005-07-23

From leakage or simply higher memory needs? Quite a difference.

Reply Parent Score: 2

RE: memory leaks
by kaiwai on Sat 16th Oct 2010 03:02 in reply to "memory leaks"
kaiwai Member since:
2005-07-06

How about the memory leak problems with FF? When I close some tabs, ideally, I'd like to see my RAM usage go down some. My FF on OSX consistently uses 600+MB ram.


That has more to do with the fact that tabs are threads rather than processes; with process separation there is the ability to reclaim memory where as with tabs in Safari and Firefox they all operate in the same memory space. What I'd like to see at the very least is some sort of garbage collection where every 5 minutes it does a quick scan of memory to clean the remains of closed tabs.

Reply Parent Score: 2

RE[2]: memory leaks
by Fergy on Sat 16th Oct 2010 05:24 in reply to "RE: memory leaks"
Fergy Member since:
2006-04-10

What I'd like to see at the very least is some sort of garbage collection where every 5 minutes it does a quick scan of memory to clean the remains of closed tabs.

A big part of that has already landed on Firefox 4 beta 7 and the rest will land on Beta 8.
http://andreasgal.wordpress.com/2010/10/13/compartments/

Reply Parent Score: 4

RE[2]: memory leaks
by dayalsoap on Sat 16th Oct 2010 05:54 in reply to "RE: memory leaks"
dayalsoap Member since:
2010-05-19

That's a good point that the tabs are all in the same address space, and you're right, they need to have some kind of sweep function that will free up the unreferenced data structures.

Reply Parent Score: 1

RE: memory leaks
by aliquis on Sat 16th Oct 2010 03:58 in reply to "memory leaks"
aliquis Member since:
2005-07-23

Reminds me how in Safari memory usage always _WENT UP_ when closing tabs, until you had no tabs left but 1+ GB of RAM allocated (not now.)

Reply Parent Score: 2

RE: memory leaks
by cb88 on Sat 16th Oct 2010 16:01 in reply to "memory leaks"
cb88 Member since:
2009-04-23

Not memory leaks... it keeps old pages cached in case you didn't mean to close them the "undo close tab" feature

Reply Parent Score: 3

RE: memory leaks
by lemur2 on Sun 17th Oct 2010 06:27 in reply to "memory leaks"
lemur2 Member since:
2007-02-17

How about the memory leak problems with FF? When I close some tabs, ideally, I'd like to see my RAM usage go down some. My FF on OSX consistently uses 600+MB ram.


Firefox did have some memory leak issues some time ago, but they fixed it. It now (Firefox 4 betas) leaks less that other browsers.

Reply Parent Score: 2