Firefox Flash plug-in has a "memory leak"

Hello folks,

Firefox is a nice and safe browser. It has nice extensions too. Alas, the Macromedia Flash plug-in tends to use more and more of your System’s RAM, it is growing and growing.
What you can do about this you read here:
http://www.help2go.com/article240.html

greets,

polonus

P changed picture

Surely this Title should be Macromedia Flash plug-in for Firefox has a memory leak ;D otherwise it is not representing the article that you are linking to and is misleading. Something that seems habit forming in your posts about anything is some way indirectly related to firefox?

[b]This particular memory leak is not the fault of Firefox [/b]- the Macromedia Flash plug-in is causing this problem!

Why would Bill Gates be laughing ?

This particular memory leak is not the fault of Firefox - the Macromedia Flash plug-in is causing this problem!

Hi,

Well of course you are right there that the leak is due to the Macromedia Flash plug-in, but the role of the Firefox browser in this. (I writing this posting in an open Firefox browser, and I have not got that particular problem here. If a browser uses a gentle 100 MB RAM for a 20 MB proggie, that is a lot. The problem is the flushing of the cache. But in a sense all browser have it in a way, browser inevitably take up more and more system mem even with relative simple JavaScripts, which may become a problem in the long run.
Making elements referring to each other, even when the user loads a new page and destroys the old “un”, the memory does not seems to be freed. Well I will take the picture out, because its off-topic nature.
Two things 1. the cause is Macromedia plug-in, 2. the cause can be opening a lot of pages with JavaScript elements referring,
the cache flushing of browsers, and FF should be better.

I hope you two can live with this.

polonus

Polonus I followed the instuctions in the article Fix Firefox Memory Leak .
I’ve been having some freeze up’s with FireFox, which could be related to Macromedia Flash plug-in ?
Maybe this about:config ‘tweak’ will solve the problem .
It will at least remedy
this memory leak !
Thanks :slight_smile: