Oh, so that's why my computer is as responsive as a boat anchor

[EyeMWing]

Text

You'd think that, after having it present since v1.2.something, they would've fixed this peg-the-CPU-and-eat-the-RAM issue. But they're content to pretend it doesn't exist.

Edit: The SS doesn't show the 99% CPU usage, which is periodic, and for whatever reason, hits both cores.

 

[mrSHEiK124]

Firefox eating 152,408 KB over here, with 7 Amazon and 2 ATOT tabs open. Seems like alot to me.

Oh, FFS, Ctrl+E jusched.exe, acrotray.exe, msmsgs.exe and qttask.exe.

 

[yobarman]

firefox is at 100+ now. Not as bad as Photoshop hogging up 700 mb

 

[Sphexi]

Got MyIE2 here, 22MB used, 10 tabs open.

 

[Raduque]

I've seen firefox climb over 300mb, but the 2.0 Beta1 hasn't gone over 190mb. But 1.3gb! :shocked: How many tabs do you have open, 70?

 

[EyeMWing]

Originally posted by: mrSHEiK124
Oh, FFS, Ctrl+E jusched.exe, acrotray.exe, msmsgs.exe and qttask.exe.

nitpicking for less than a meg and next to ZERO CPU time, when some lazy opensores developer is content to just randomly grab a gig and a half to render ONE tab?

 

[EyeMWing]

Originally posted by: Raduque
I've seen firefox climb over 300mb, but the 2.0 Beta1 hasn't gone over 190mb. But 1.3gb! :shocked: How many tabs do you have open, 70?

One. It's a bug. A huge, glaring bug that's been there since I started using the damned app. Let it sit for a few days, and it'll steal your megabytes!

 

[sniperruff]

Originally posted by: EyeMWing

Originally posted by: Raduque
I've seen firefox climb over 300mb, but the 2.0 Beta1 hasn't gone over 190mb. But 1.3gb! :shocked: How many tabs do you have open, 70?

One. It's a bug. A huge, glaring bug that's been there since I started using the damned app. Let it sit for a few days, and it'll steal your megabytes!

so close it. big whoop.

 

[AgaBoogaBoo]

Originally posted by: EyeMWing

Originally posted by: Raduque
I've seen firefox climb over 300mb, but the 2.0 Beta1 hasn't gone over 190mb. But 1.3gb! :shocked: How many tabs do you have open, 70?

One. It's a bug. A huge, glaring bug that's been there since I started using the damned app. Let it sit for a few days, and it'll steal your megabytes!

Agreed, they won't admit to the issue either.

 

[EyeMWing]

Originally posted by: sniperruff

Originally posted by: EyeMWing

Originally posted by: Raduque
I've seen firefox climb over 300mb, but the 2.0 Beta1 hasn't gone over 190mb. But 1.3gb! :shocked: How many tabs do you have open, 70?

One. It's a bug. A huge, glaring bug that's been there since I started using the damned app. Let it sit for a few days, and it'll steal your megabytes!

so close it. big whoop.

That's all well and good if you're average joe who browses the internet. But there are cases where a web browser has a damn good reason to be left open - kiosks, administrative applications, web app consoles.

I've actually steered a project in development away from using Firefox in favor of IE because of this very bug - the application requires 100% uptime - having a tech reboot the machine daily because it's out of RAM isn't an acceptable state.

 

[GeekDrew]

Originally posted by: EyeMWing

Originally posted by: sniperruff

Originally posted by: EyeMWing

Originally posted by: Raduque
I've seen firefox climb over 300mb, but the 2.0 Beta1 hasn't gone over 190mb. But 1.3gb! :shocked: How many tabs do you have open, 70?

One. It's a bug. A huge, glaring bug that's been there since I started using the damned app. Let it sit for a few days, and it'll steal your megabytes!

so close it. big whoop.

That's all well and good if you're average joe who browses the internet. But there are cases where a web browser has a damn good reason to be left open - kiosks, administrative applications, web app consoles.

I've actually steered a project in development away from using Firefox in favor of IE because of this very bug - the application requires 100% uptime - having a tech reboot the machine daily because it's out of RAM isn't an acceptable state.

I know that there are issues with Firefox, and it's far from perfect... but what *exactly* are you doing, other than just leaving it open, to cause it to use so much RAM? I've intentionally left a browser window open for 2 solid weeks, and it was still under 100 MB used.

 

[Baked]

Just opened 10 tabs to different websites. 91MB. FF 1.5.06. I got lots of RAM to spare out of the 1GB.

 

[EyeMWing]

Originally posted by: GeekDrew

Originally posted by: EyeMWing

Originally posted by: sniperruff

Originally posted by: EyeMWing

Originally posted by: Raduque
I've seen firefox climb over 300mb, but the 2.0 Beta1 hasn't gone over 190mb. But 1.3gb! :shocked: How many tabs do you have open, 70?

One. It's a bug. A huge, glaring bug that's been there since I started using the damned app. Let it sit for a few days, and it'll steal your megabytes!

so close it. big whoop.

That's all well and good if you're average joe who browses the internet. But there are cases where a web browser has a damn good reason to be left op ( n - kiosks, administrative applications, web app consoles.

I've actually steered a project in development away from using Firefox in favor of IE because of this very bug - the application requires 100% uptime - having a tech reboot the machine daily because it's out of RAM isn't an acceptable state.

I know that there are issues with Firefox, and it's far from perfect... but what *exactly* are you doing, other than just leaving it open, to cause it to use so much RAM? I've intentionally left a browser window open for 2 solid weeks, and it was still under 100 MB used.

Leaving it open. And that's it. Not everyone encounters the issue - but for those who do, it persists. It seems to happen much more frequently on computers with large amounts of RAM (>1gb)

 

[imported_LoKe]

Turn the tweak on for trim.on.minimize. It'll dump the usage whever you...minimize.

 

[ultimatebob]

I've been having problems with the newer builds of Firefox causing my hard drive to go nuts for a minute or two while it's clearing out my cache after I start it every day. I was able to fix that by decreasing my cache size from 50 MB to 5 MB, though. It's still annoying, though, and I've never had that problem while using IE.

 

[EyeMWing]

Originally posted by: LoKe
Turn the tweak on for trim.on.minimize. It'll dump the usage whever you...minimize.

Tried it before - it doesn't.

Amusingly, there seems to be something about ATOT causing it to eat 1.5gb. Because I just restarted the browser SEVERAL times, and it's still sucking down all that RAM.

 

[Rubycon]

Originally posted by: EyeMWing

Amusingly, there seems to be something about ATOT causing it to eat 1.5gb. Because I just restarted the browser SEVERAL times, and it's still sucking down all that RAM.

Must be that Crucial Ad making FF suck all the memory so people buy more memory!

 

[iRONic]

Originally posted by: EyeMWing
Text

You'd think that, after having it present since v1.2.something, they would've fixed this peg-the-CPU-and-eat-the-RAM issue. But they're content to pretend it doesn't exist.

Edit: The SS doesn't show the 99% CPU usage, which is periodic, and for whatever reason, hits both cores.

Borked extensions?

 

[Platypus]

The trim works well for me, I'm one of the 100MB after 10 minutes open with 3 tabs crowd and this tweak makes it go down to 3MB when it's minimized.

 

[EyeMWing]

Originally posted by: iRONic

Originally posted by: EyeMWing
Text

You'd think that, after having it present since v1.2.something, they would've fixed this peg-the-CPU-and-eat-the-RAM issue. But they're content to pretend it doesn't exist.

Edit: The SS doesn't show the 99% CPU usage, which is periodic, and for whatever reason, hits both cores.

Borked extensions?

That would be difficult, as I have NONE installed.

 

[potato28]

Ohhh the how high can we get the mem usage game? And FYI, the new update is causing this. 1.5.0.6 is coming out in a few days anyways...

 

[cKGunslinger]

I posted this a few months ago.

Text

And I've only seen similar/better performance since then. What are you guys doing to your poor FF installations?

 

[EyeMWing]

Originally posted by: potato28
Ohhh the how high can we get the mem usage game? And FYI, the new update is causing this. 1.5.0.6 is coming out in a few days anyways...

Actually, just for shits and giggles, I just installed the new update. Or tried to. FF now crashes on load with the error "ZOMG I CAN'T INSTALL THE UPDATE" and retries until you kill the process.

Now posting from IE6.

 

[Goosemaster]

Originally posted by: EyeMWing

Originally posted by: potato28
Ohhh the how high can we get the mem usage game? And FYI, the new update is causing this. 1.5.0.6 is coming out in a few days anyways...

Actually, just for shits and giggles, I just installed the new update. Or tried to. FF now crashes on load with the error "ZOMG I CAN'T INSTALL THE UPDATE" and retries until you kill the process.

Now posting from IE6.

 

[GeekDrew]

Originally posted by: EyeMWing

Originally posted by: GeekDrew

Originally posted by: EyeMWing

Originally posted by: sniperruff

Originally posted by: EyeMWing

Originally posted by: Raduque
I've seen firefox climb over 300mb, but the 2.0 Beta1 hasn't gone over 190mb. But 1.3gb! :shocked: How many tabs do you have open, 70?

One. It's a bug. A huge, glaring bug that's been there since I started using the damned app. Let it sit for a few days, and it'll steal your megabytes!

so close it. big whoop.

That's all well and good if you're average joe who browses the internet. But there are cases where a web browser has a damn good reason to be left op ( n - kiosks, administrative applications, web app consoles.

I've actually steered a project in development away from using Firefox in favor of IE because of this very bug - the application requires 100% uptime - having a tech reboot the machine daily because it's out of RAM isn't an acceptable state.

I know that there are issues with Firefox, and it's far from perfect... but what *exactly* are you doing, other than just leaving it open, to cause it to use so much RAM? I've intentionally left a browser window open for 2 solid weeks, and it was still under 100 MB used.

Leaving it open. And that's it. Not everyone encounters the issue - but for those who do, it persists. It seems to happen much more frequently on computers with large amounts of RAM (>1gb)

I've used Firefox extensively on machines w/ 512MB, 1GB, 1.5GB, and 2GB of RAM. None of them have exhibited the problem.