Using Pale Moon 64bit,Have a Memory Exposion After 6hrs!

[dv8cowboy]

Hi,everyone,

Palemoon 12 64bit is my preferred Browser BUT:

Running 15-25 tabs for longer than 6 hours and the builtup Memory explosion occurs and Pale Moon either crashes or Freezes.I also use FireFox 13beta with NONE of these issues! Might some developer look at the coding for FF 13beta and get some ideas as to how to control the inherent memory problem for Pale Moon 64bit?? I don't need to hear workarounds,which I already know.That just ignores the real problem with coding Pale Moon 64bit! Please address the memory leaks and loss of memory control! I also use Pro Lasso Pro for Process management and still after running Pale Moon as a below normal process and trimming memory processes,it tears thru RAM!

Any ideas if these sorts of things are being worked on?...I gave FireFox 13beta as a GOOD example of memory management.This really needs to be fixed...


-Cheers from Australia
-Cowboy

[satrow]

Hi Cowboy,

I've had Pale Moon x64 open for close to 8 hours now, from 2-30+ tabs at any one time; I opened 24 at the same time early on, a minimum of 25 sites/27 tabs open for at least 6.5 hours - I don't see any sign of any excessive memory usage, my Peak Working Set is at 700MB, I'd say that was pretty normal for a 64-bit browser on my PC with 6GB of RAM.

I suggest you look to your extensions, profile or possibly a buggy site in your mix. about:memory might also be of some use.

[dv8cowboy]

Been there don that cymroly!
...my point is that no extention or plugin takes away from the need to look at memory management as a developer issue.I gave FireFox13beta as a good example of memory managemet.Perhaps the coders might look at FF13beta and get some scripts that come out in a Pale Moon 13 release!
....I have 8megs of ram but hate Pale Moon64 memory leakages,seems to NOT release memory deleting tabs??!!

-Cowboy

Hi Cowboy,

I've had Pale Moon x64 open for close to 8 hours now, from 2-30+ tabs at any one time; I opened 24 at the same time early on, a minimum of 25 sites/27 tabs open for at least 6.5 hours - I don't see any sign of any excessive memory usage, my Peak Working Set is at 700MB, I'd say that was pretty normal for a 64-bit browser on my PC with 6GB of RAM.

I suggest you look to your extensions, profile or possibly a buggy site in your mix. about:memory might also be of some use.

[Moonchild]

...my point is that no extention or plugin takes away from the need to look at memory management as a developer issue.

If an add-on, because of poor add-on programming, doesn't release memory or the container properly when you close a tab, that is the add-on's problem, not the browser's problem. You can potentially force the release by simply cutting the container away but that will likely break the add-on in its entirety (and likely also browser controls that are hooked into by the add-on). It's not that simple, and either way the add-on has to be fixed.

As an analogy: If I write a driver for Windows that causes a Blue Screen, does that mean that Windows needs to be looked at? No, it means the driver needs to be fixed. Any changes in Windows to mitigate this will be extremely involved and would need a rewrite of parts of the kernel, in the process requiring a rewrite of other drivers that rely on the current way of working (think of the transition Win XP -> Vista)

FF13beta is no better of an example than 12.0-release, in the add-on memory respect. ALSO: If you compare FF13beta (x86) and it works better for you, then you are probably better off switching to Pale Moon x86 (since it may likely be a system-level leak (and not an application-level leak) resulting from using accelerated graphics in native x64 mode, which I have seen several times already).

about:memory might also be of some use.

I second this; it will point at which page/tab causes the issue and what subsystem the memory disappears into, with some luck.

Memory use that goes out of bounds, especially on x64, but on any recent version of the Mozilla code, can be caused by a lot of different things: add-ons, plugins in OOP, plugins inside the browser (Java), graphics drivers, third party programs that hook into the browser (skinning, etc), incompatible themes, ...

[dv8cowboy]

I just may have to do that Moonchild,since the Pale Moon 64 isn't 'baked' yet!....we'll have to see in the future.Oh, I have FF13beta set with exactly the same addons and plugins as I do Pale Moon64...


-Cowboy

[Moonchild]

Well, without more information from your side, there's nothing that can be looked at for your "explosion". You obviously missed my point that Pale Moon x64 uses a different execution environment than x86 (WoW64) that comes with its own set of quirks. Doesn't mean it's 'not baked', it just means that running x64 native is not for the faint of heart. There is a reason why the Mozilla Corporation doesn't officially release current release channel Firefox binaries in x64. A lot of system vendor drivers are simply not ready yet to have it work for 'everyone'.