I watched using about:cache?device=memory, but I never saw an image being unloaded (html-files, yes). It seems that Adblock prevents *every* image in the memory-cache from being uloaded - even when it's disabled, or when no image-blocking rule was active (the default immediately installing Adblock). Yes, using Adblock v.5 d3 * nightly 41 (although it's labelled as 40 in the preferences window). > Jo Hermans, are you still experiencing severe memory leak by Adblock even after > Adblock 0.5.3.040 was released on Januat. > the one that is automatically downloaded. > The problem is that the advertised version is Adblock 0.5.2.056, which is also And that's the one with the biggest, easiest reproduceable bug (just use, memory will never be released). When you try to upgrade to a new version with the update-mechanism, this is the latest version available. The problem is that the advertised version is Adblock 0.5.2.056, which is also the one that is automatically downloaded. > Jo Hermans, is your '0.5 d3 nightly 40' the Adblock 0.5.3.040? > Adblock 0.5.2.056 has a memory leak problem. > Go to the site below for the latest Adblock 0.5.3.040. > And a comment on Decemsays(as of today, this is put in page 5) > AdBlock currently available at is Adblock 0.5.2.056 which > these should work in 1.5) never seem to release items from the memory cache. Note that the latest version of Adblock (both 0.5.2.056 and 0.5 d3 nightly 40

Firefox flash plugin memory leak