Frank-Rainer Grahl wrote:
└──-2,644.69 MB (-158.38%) ── heap-unclassified [?!]
If you press GC under Free Memory does it get back to normal?
No. I also tried the "minimize memory" there. After running these the
memory figures were still as bad if not worse.
You can send me the report together with the output of about:support
(use copy text to clipboard). I am no expert here so don't have high hopes.
I will send you a copy.
Did you try Adrians 2.49 yet? TB fixed some long standing issues in
2.49. I had trouble with IMAP access prior to 2.49 and even saw a crash
now and then. Very stable now. Also 2.48 is the first version using
cache2 as the default. There might be some additional fixes in 2.49.
I have not as yet tried it. Only a manual install is available at
present, so I was waiting on Ubuntuzilla to get back to a "normal"
update method.
Dave
FRG
David H. Durgee wrote:
Looking at the memory report in the browser I see the following:
└──-2,644.69 MB (-158.38%) ── heap-unclassified [?!]
The memory figure is highlighted in red, so I assume this is a
problem. I have the memory report saved and can make it available to you.
Dave
Frank-Rainer Grahl wrote: Maybe you can check with about:memory and
open a bug if you find something.
For me I found that Amazon seems to cause some problems over time.
These are likely Gecko problems and will also occur in Firefox but
probably some might be SeaMonkey or extension specific.
FRG
David H. Durgee wrote:
I am currently running Adrian's 64 bit build on linux mint 17.2 x64
and am noticing what I can only assume is a memory leak over time. I
just had to restart SM when my system usage showed it using 1.7GB of
memory! After restarting it now reports 725MB used, so this is quite
an improvement.
I tend to avoid restarts until necessary as I keep multiple tabs open
and some of them require me to login again after a restart. Perhaps
it would be possible to do a "softer" restart of some sort at some
point and avoid this?
I know that security issues are primary, but can memory leaks be
looked into at some point? If they can't be addressed easily, as they
might be specific to particular builds as opposed to general, then
perhaps at least it might be possible to implement some sort of a
"restart" option that would avoid the problems associated with a
complete shutdown/launch cycle imposes?
Dave
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
