Anyway . . . what's it like for you?

My god.satrow wrote:. . . currently I'm using some 2.5GB . . .
Interesting. When I start up PaleMoon 12.3, it starts off using 55-65MB and 25% CPU, then drops to between 30-40MB and 0-2% CPU and stays there. If I open this thread in a tab, it goes up to 59MB (and 57-58MB if I have ImageBlocker2.1 on). This is on Windows 7 Starter 32-bit with no addons and 1GB of RAM. I think the browser might make use of more memory for speed if you have more RAM (like Windows 7) but I'm not sure. How much RAM does your computer have Night Wing?Night Wing wrote:I'm running the 32-bit version of PM. Right now, with no tabs open, PM is using 97MB.
Just curious, in what way does Gmail "leak"? Do you mean your memory grows and grows if you leave your Inbox open in a tab for a long time, or it grows more than it shrinks if open it in a new tab then close the tab? In both cases, mine seems to go up and down in a pretty balanced way over time so far (tried opening and closing Inbox 10 times in a new tab, then leaving one Inbox tab open for around 20 minutes).satrow wrote:UPDATE: looks like Gmail was the #1 candidate for the memory leak.
In my case, I was composing an email and I'd had the tab open for several days - most of the content won't be of use until probably March/April of next year, so I was in no rush to finish it - it was probably the regular auto-saving of that draft email that caused the memory usage to keep creeping ever upwards.ninaholic wrote:Just curious, in what way does it "leak"? Do you mean your memory grows and grows if you leave your Inbox open in a tab for a long time, or it grows more than it shrinks if open it in a new tab then close the tab? In both cases, mine seems to go up and down in a pretty balanced way over time so far (tried opening and closing Inbox 10 times in a new tab, then leaving one Inbox tab open for around 20 minutes).satrow wrote:UPDATE: looks like Gmail was the #1 candidate for the memory leak.
My main computer installed with Windows 7 Ultimate, 64-bit has 24 GB of memory. My backup computer installed with Windows 7 Home Premium, 64-bit has 16 GB of memory.ninaholic wrote:I think the browser might make use of more memory for speed if you have more RAM (like Windows 7) but I'm not sure. How much RAM does your computer have Night Wing?
hopefully this will be alleviated by PM 15. A new patch for leaky addons has been added.Pnume wrote:My ram consumption ranges from 150 MB (once I start Pale Moon) to 550 MB or so (after I've been doing lots of browsing and have opened lots of tabs). 550 MB may seem like a lot to some of you, but I use lots of add-ons.
Anyway . . . what's it like for you?
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 helpstravinsky wrote:hopefully this will be alleviated by PM 15. A new patch for leaky addons has been added.
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.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)
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).stravinsky wrote: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.