RadiclDreamer
Diamond Member
- Aug 8, 2004
- 8,622
- 40
- 91
I dont think I've ever had FF use over 100-150MB ram, if you get that kind of usage, its an extension
Originally posted by: SilentZero
.5/10
Open software in morning.Originally posted by: Crusty
Caching data != 'memory leak'
Originally posted by: 0roo0roo
chrome=24 tabs 670mb
firefox=134tabs 544mb
course firefox has extensions that block annoying flash/shock wave nonsense which helps
Originally posted by: MikeyIs4Dcats
Originally posted by: 0roo0roo
chrome=24 tabs 670mb
firefox=134tabs 544mb
course firefox has extensions that block annoying flash/shock wave nonsense which helps
what do you do with 134 tabs??
Originally posted by: 0roo0roo
Originally posted by: MikeyIs4Dcats
Originally posted by: 0roo0roo
chrome=24 tabs 670mb
firefox=134tabs 544mb
course firefox has extensions that block annoying flash/shock wave nonsense which helps
what do you do with 134 tabs??
its not that i use a ton of tabs all at once. sometimes clutter builds up if you leave your pc/browser open for days/weeks at a time. having a lot of ram makes it not something to worry about. its not like the olden days where you closed programs all the time to conserve ram.
Originally posted by: mrSHEiK124
Then there needs to be a cache flush button, because it is a fucking memory leak when somehow the Shockwave Flash process running under Chrome is using 72236k to display one tab of Engadget ads and four tabs of ATOT ads. I know I don't have 70 MB of ads open, otherwise these pages would've taken more than a few seconds a piece to load. Closing Engadget brings it down to 72172k, closing some Amazon tabs somehow brings Flash usage UP to 72648k, and closing more ATOT tabs makes it 77648k.Originally posted by: Crusty
Caching data != 'memory leak'
Originally posted by: CKent
I have 2gb ram with Win XP pro and it's more than enough. FF is eating ~150mb with a few tabs open. Maybe you have some kind of weird virus?
Originally posted by: n7
I love my Firefox, but it does devour RAM sometimes.
Especially if i leave it with multiple tabs open for days...i've seen it do 500+ MB.
Time for 8 GB OP![]()
Just get married... but I don't see what that has to do with RAM or why this isn't in L&ROriginally posted by: mrSHEiK124
Then there needs to be a cache flush button
Originally posted by: GodlessAstronomer
Originally posted by: mrSHEiK124
Then there needs to be a cache flush button, because it is a fucking memory leak when somehow the Shockwave Flash process running under Chrome is using 72236k to display one tab of Engadget ads and four tabs of ATOT ads. I know I don't have 70 MB of ads open, otherwise these pages would've taken more than a few seconds a piece to load. Closing Engadget brings it down to 72172k, closing some Amazon tabs somehow brings Flash usage UP to 72648k, and closing more ATOT tabs makes it 77648k.Originally posted by: Crusty
Caching data != 'memory leak'
Wow, are you serious? Flash is a run time environment! It means that small files can be transmitted because the runtime contains the library code that is being called, so every library called by the client software in the Flash runtime has to be loaded into memory when Flash content is displayed. Combine this with runtime cache, stack frame buffers/padding and other bits of memory usage, 70mb is nothing. This thread is riddled with dickscarfery.
Originally posted by: mrSHEiK124
Originally posted by: GodlessAstronomer
Originally posted by: mrSHEiK124
Then there needs to be a cache flush button, because it is a fucking memory leak when somehow the Shockwave Flash process running under Chrome is using 72236k to display one tab of Engadget ads and four tabs of ATOT ads. I know I don't have 70 MB of ads open, otherwise these pages would've taken more than a few seconds a piece to load. Closing Engadget brings it down to 72172k, closing some Amazon tabs somehow brings Flash usage UP to 72648k, and closing more ATOT tabs makes it 77648k.Originally posted by: Crusty
Caching data != 'memory leak'
Wow, are you serious? Flash is a run time environment! It means that small files can be transmitted because the runtime contains the library code that is being called, so every library called by the client software in the Flash runtime has to be loaded into memory when Flash content is displayed. Combine this with runtime cache, stack frame buffers/padding and other bits of memory usage, 70mb is nothing. This thread is riddled with dickscarfery.
I don't care if it's french fucking toast. Nothing should be using 100 MB of RAM to display 1 MB worth of data. That's shitty coding, and Flash is ridiculous in the sense that it can bring a reasonably fast single core processor to it's knees if you try and scroll on any pages with Flash ads. If 5 seconds worth of looping vector images needs 100 MB of RAM, I'd say fuck it and animate some uncompressed images just to say I did. Are you seriously trying to argue that Flash does not in fact suck moldy asshole?
