Massive Memory Leak in Firefox 2.0.0.3

Alistair · Mar 23, 2007, 03:57 PM

Has anyone else been forced into downgrading back to 2.0.0.2 as a result of a massive memory leak in the latest "bug fix"? At least myself (on two separate computers) and one friend have had Firefox take a HUGE amount of memory in a short period of time (600+MB, with MASSIVE swapping going on). It seemed to happen when browsing with multiple tabs and some flash in them. Its obviously a 2.0.0.3 issue as this does NOT happen in 2.0.0.2 for me. Just curious is anyone else has seen this or has more information on it.

Erroneus · Mar 23, 2007, 04:45 PM

No problem here, using 2.0.0.3 on two machines. Sounds like a plugin or an extension going crazy.

Using latest flash and java 6.0 on both machines, plus a ton of extensions.

>GSXR<mrbusa · Mar 23, 2007, 04:51 PM

Me to.
Two machines and countless extensions and themes and no issues. It is using less than 50mb with four tabs open and flash enabled.

Mousey · Mar 23, 2007, 06:15 PM

i dunno i never checked, looks like you've given me something to look into.
i run FF 2.0.0.3 with no themes and only DownThemAll! (DL Accelerator)

MGaz · Mar 24, 2007, 07:40 AM

well ATM fire fox is eating up 120 MB's of system memory. that's nothing compared to how it was one day.. i'll see if i can find the screen shot i took.

My PC crawled to an almost halt.

in fact i think it slowed down so much it actually started going backwards! lol

MGaz · Mar 24, 2007, 08:01 AM

well ok, dummy me didn't take a pic of the memory usage, like i thought, but i can tell you it was a lot of my 1 gig.

What i did take a pic of was the cpu usage, my PC was crawling along

.

FF 92% cpu usage! somethings wrong there? surely? I never had that kind of problem with IE, all IE ever use to do was crash and chuck up errors and illegal operations all the time. Silly MS garbage.

Anyway, heres the pic:

Alistair · Mar 24, 2007, 11:14 AM

MGaz, thats exactly what it did to a friend and I once it started using the hard drive for swapping.

aNy_oNE · Mar 25, 2007, 02:51 AM

MGaz, firefox goes to about 99% cpu usage for me if im loading 3-4+ tabs at once, not uncommon. (although my CPU is crap, even compared to yours xD)

PangingJr · Mar 25, 2007, 04:16 PM

have you tried creating a new Firefox profile, or clean out the existing profile (only leave what you need, likes cookies, bookmarks files) ?

cozumel · Mar 25, 2007, 05:20 PM

I don't have any problems here with FF 2.0.0.3. Working perfectly.

H3X4D3C1M4L · Mar 26, 2007, 12:47 AM

Quote:

Originally Posted by MGaz

well ATM fire fox is eating up 120 MB's of system memory. that's nothing compared to how it was one day.. i'll see if i can find the screen shot i took.

My PC crawled to an almost halt.

in fact i think it slowed down so much it actually started going backwards! lol

Time for an upgrade

...upgrade of browser that is. FF does this with alot of tabs open, if I have like 30 tabs open my PC grinds to absolute 0 power.

Never had this problem with Opera, never dared try with IE

GutterPunk · Mar 29, 2007, 08:01 AM

I had 53 tabs open in IE w/o a problem.

FF yes the same problem and opera is ok

PangingJr · Mar 29, 2007, 11:03 AM

i use this below Firefox build in Vista right now...
Tete's Firefox 2.0.0.3 [2007032116 en-US win32 tete009 sse pgo]
Visual C++ 2005 SP1 (PGO) build, and CPU Instruction Set SSE3 Beta DLL (December 8, 2006) - http://www1.plala.or.jp/tete009/en-U...html#FFRELEASE

when tested with no Add-ons, no Flash (Proxomitron), and with 50 tabs opened, i can hardly see any system performance drop off/down.

GutterPunk · Mar 29, 2007, 12:01 PM

I wonder, I tested mine on XP

Im going to go home and test it on my Vista

Alistair · Apr 12, 2007, 11:30 AM

I have managed to come up with a way to trigger this memory leak on a consistent basis.

Step 1: Open Task Manager and sort by memory usage. (CTRL+SHIFT+ESC)
Step 2: Open Firefox
Step 3: Browse to a website
Step 4: Open new browser tab (CTRL+T)
Step 5: Navigate to chrome://browser/content/browser.xul
Step 6: Right-Click View Source
Step 7: Close View Source Window
Step 8: Close Tab opened above.
Step 9: Sit back and watch your memory usage climb.