To: CalvaryJohn
“But its a bit of a memory hog” that is a WINDOWS Problem not Firefox
19 posted on
02/03/2010 8:45:25 AM PST by
eyeamok
To: eyeamok
But its a bit of a memory hog that is a WINDOWS Problem not Firefox That's incorrect. Each application is responsible for releasing the memory it used when the application is closed. It is ALWAYS an application problem not a Windows problem. (not a fanboy, just a programmer)
32 posted on
02/03/2010 8:53:47 AM PST by
BubbaBasher
("Liberty will not long survive the total extinction of morals" - Sam Adams)
To: eyeamok
I wasn’t aware of that, but it makes sense. Microsoft is the king of bloatware.
37 posted on
02/03/2010 8:59:51 AM PST by
CalvaryJohn
(What is keeping that damned asteroid?)
To: eyeamok
But its a bit of a memory hog that is a WINDOWS Problem not Firefox
No, it is Firefox. You can watch Firefox, even sitting idle, consume more and more memory, if you watch it through the Processes tab of Windows Task Manager. Right now, my Firefox is consuming 156,180K and I have only 1 tab on a simple (no flash or motion graphics) website open. I closed that tab to blank and it is now consuming 166,316K.
41 posted on
02/03/2010 9:04:54 AM PST by
TomGuy
To: eyeamok
that is a WINDOWS Problem not Firefox Far be it for me to defend Windows, but in this case, you're incorrect.
From a developer's percpective, memory usage/bloating/leaks are generally the application's fault, not the operating system. There are exceptions (if you're using an OS library that has issues, or some such) but those are rare.
To this particular instance: I have a dual-boot laptop that I use constantly (XP and Ubuntu Linux) and I have a Mac Mini that I use at home. FireFox is a memory hog on all three platforms.
63 posted on
02/03/2010 10:39:19 AM PST by
Egon
(The difference between Theory and Practice: In Theory, there is no difference.)
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson