News for hackers. Stuff that matters.
Re:Firefox 5 Details: Social Sharing, Extension Integration by DarkShikari on Sunday April 03, 2011 @04:53PM (#2403958)
And my Firefox 4 periodically OOM-crashes on Windows 7. It's also extremely overzealous in its allocation of decompressed graphics buffers (far worse than Firefox 3.5), so it typically uses upwards of 2GB of RAM for a set of tabs that previously only used 1GB.

Sometimes if I have tabs with a lot of large images open, Firefox will start up, allocate up to the 32-bit limit on Windows (~3GB)... then deallocate all the graphics buffers and drop down to 1GB. This process can take upwards of 5 minutes.

They blame the memory leaks on extensions, but if there's no way to see which extensions are using the memory besides a month-long exhaustive search (it typically take days to leak enough memory to crash), how are we to know?

Re:Firefox 5 Details: Social Sharing, Extension Integration by pcwalton on Sunday April 03, 2011 @05:23PM (#2404108)
There is work underway to make the new extension system (Jetpack) load extensions out-of-process. This will make it easy to see how much memory each extension is using. Unfortunately, add-ons built using the traditional system will still be in-process. Most of them depend on being able to synchronously dive into the page or browser DOM and mess with it, which makes accounting hard.

The 32-bit Windows graphics thing sounds like a bug. Setting max-concurrent-tabs in about:config to 0 may help.