Re: memory leaks in SeaMonkey 2.48

On 4/5/17 3:33 PM, Mason83 wrote: On 28/03/2017 20:58, Mason83 wrote: On 28/03/2017 18:09, 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

Re: memory leaks in SeaMonkey 2.48

On 28/03/2017 20:58, Mason83 wrote: > On 28/03/2017 18:09, 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. >>

Re: memory leaks in SeaMonkey 2.48

> Does that mean that the site where one downloads SeaMonkey is going to > change? No its an internal thing. The bata builds are done but now comes the fun part of moving them to the right places so might need another build:

Re: memory leaks in SeaMonkey 2.48

On 31/03/2017 4:47 AM, EE wrote: Frank-Rainer Grahl wrote: Still probably at least 3-4 weeks away. Ewong is currently on 2.48 beta to iron out switching to new distribution servers and we bad infrastructure issues galore. The beta will be followed by a regular 2.48 and then hopefully a 2.49

Re: memory leaks in SeaMonkey 2.48

Frank-Rainer Grahl wrote: Still probably at least 3-4 weeks away. Ewong is currently on 2.48 beta to iron out switching to new distribution servers and we bad infrastructure issues galore. The beta will be followed by a regular 2.48 and then hopefully a 2.49 from the ESR tree fast. Does that

Re: memory leaks in SeaMonkey 2.48

On 28/03/2017 18:09, 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

Re: memory leaks in SeaMonkey 2.48

> > 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. Still probably at least 3-4 weeks away. Ewong is currently on 2.48 beta to iron out switching to new distribution servers and we bad

Re: memory leaks in SeaMonkey 2.48

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

Re: memory leaks in SeaMonkey 2.48

>└──-2,644.69 MB (-158.38%) ── heap-unclassified [?!] If you press GC under Free Memory does it get back to normal? 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. Did you try Adrians 2.49

Re: memory leaks in SeaMonkey 2.48

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:

Re: memory leaks in SeaMonkey 2.48

I waited a bit after restarting SeaMonkey and now that it appears to be eating a lot of memory ran the about:memory as suggested. The report does appear to show some problems with memory management as there were red highlighted entries. I have never looked at this before, but it appears to

Re: memory leaks in SeaMonkey 2.48

TCW wrote: On Tue, 21 Mar 2017 16:12:30 -0400, "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

Re: memory leaks in SeaMonkey 2.48

Hmm two seem to be startup crashes. I think there were some problems recently solved in Gecko / Firefox. Need to check if we picked up all patches there. But running 2.50 for quite some time now in a vm and didn't experience them yet. Third is a problem with some Nvidia dll. If not done yet

Re: memory leaks in SeaMonkey 2.48

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

Re: memory leaks in SeaMonkey 2.48

2.50 has a few problems but didn't crash on me yet. Any specifics? FRG TCW wrote: I'm on 2.50 (Winx64) myself but it's crashy as heck but no leakage that I can see like with the older versions. ___ support-seamonkey mailing list

Re: memory leaks in SeaMonkey 2.48

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

memory leaks in SeaMonkey 2.48

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