What memory range does your Pale Moon consume?

[Pnume]

I'm really looking forward to PM 15. Things have been slow recently; I suspect memory leaking add-ons are the culprits.

[Moonchild]

hopefully this will be alleviated by PM 15. A new patch for leaky addons has been added.

Overall I don't think there are all that many add-ons that are leaky in the way that would be helped by the zombie-container fix, but I guess it'd help
Pale Moon with a lot of add-ons will still consume a good chunk of memory, it's just the way it is. Can't have the cake (super-extended browser with loads of extra functionality) and eat it too (fit it in 100 MB)

[Pnume]

Speaking of PM 15: Do you have any release date estimates, Moonchild?

Firefox 15 is at beta 2 right now (as you probably already knew).

[stravinsky]

Pale Moon with a lot of add-ons will still consume a good chunk of memory, it's just the way it is. Can't have the cake (super-extended browser with loads of extra functionality) and eat it too (fit it in 100 MB)

yes. But to make addons use less memory isnt the aim of this patch, AFAIK. Its to allow the browser to reclaim the memory after the addon has done its work and the windows has been closed.

[Moonchild]

yes. But to make addons use less memory isnt the aim of this patch, AFAIK. Its to allow the browser to reclaim the memory after the addon has done its work and the windows has been closed.

No, the patch is to forcefully reclaim allocated objects that "bad" add-ons don't release after the page/tab has been closed. It only applies to add-ons that don't do good housekeeping, to clean up after them. It's actually a rather rigorous method but considering the add-ons don't have any business trying to access what should have been released, from a browser point of view, it's safe. You can expect a lot of add-ons to need updates for v15 though as they may simply break. In fact, some of the internal Firefox UI code broke in major ways because of the patch (It's why I couldn't back-port it to v12).