WaltS48 wrote:
On 5/21/20 3:38 PM, Frank-Rainer Grahl wrote:
Ant wrote:
On 5/20/2020 3:49 PM, Frank-Rainer Grahl wrote:
Ant wrote:
On 5/20/2020 10:00 AM, Doors wrote:
On Sun, 17 May 2020 05:40:47 -0700, flyguy <[email protected]>
wrote:
Windows 10, SM 2.49.4
Task Manager showed SM using 32% memory with email and one browser
window open.
The browser had only one tab with the Washington Post front page.
Closing the
browser reduced memory use to 24%; after closing the email then
reopening it, it
used only 7%. I've noticed this high memory usage before. Is there a
way to avoid
it, or to reduce it without closing the program? I don't mind
closing/reopening
the email, but often I have several windows and tabs open, so it's a
nuisance to
close the browser, too.
It isn't just you.
SM has always been a memory hog.
I run it with disk cache disabled, set to 1Mb that is.
Prefetching disabled, check page on every load.
It exceeds 2Gb for me daily, at times spiking to 4Gb.
Thank goodness for the restart button.
The pattern I have noticed indicates not all memory is released when a
page is closed.
If a page takes 150Mb to render, 25-50Mb is not released.
It could be an incomplete release list, or some automatic allocator that
fails to report memory usage correctly.
Not that FF is much better behaved.
No idea on chrome, I won't allow it on my system.
Still better than the mess that is FF.
I am so glad I can kill tabs, I hate those things.
Ditto. SM v2.53.2 and earlier still use old Gecko's web browser engine. I
was told v2.57 uses the newer one that current Firefox uses. It still has
a long way to go before it's stable for the public though. :( I have to
exit and restart my SeaMonkey often because of bloated web sites like
YouTube, LinkedIn, Facebook, Twitter, Reddit's new design (old design is
fine), etc. It really hogs resources like memories, CPU, etc. SeaMonkey
even freezes and sometimes get stuck forever! It doesn't even take long
too for these issues to come up too! :(
Ther is no new web browser engine. Actually 2.53.x has many backports
here. 2.57 and up are not really faster. Just bloated sites these days.
Oh. Firefox's newer Geck web engine is much faster than the one in
SeaMonkey. :(
There is no new web engine.
FRG
So Gecko 78 with all the mozilla-central commits wouldn't be a new and
improved Gecko engine?
Improved yes but not new. Rip enough functionality out, dumb down the ui with
primitive black and white svg graphics (fast because vector graphics) and put
bogus blocking stuff in it in the name of privacy which prior to this was done
by extensions like uBlock and NoScript and you get: A faster browser.
Surprise! Most of it possible because of e10s which doesn't block the ui and
unfortunately neither TB nor SeaMonkey has yet.
I am the last one saying that SeaMonkey rendering is faster or better but
Chromium Edge still runs circles around both Fx and SM.
I think 76 may also have some improvements like WebRender for some Windows
users on modern Intel laptops with a small screen for improved graphics
rendering.
Yes unless you run with a buggy graphics driver which, in my opinion is the
case for all Intel chips and older AMD/Nvidia drivers. Rust and webrender to
the rescue! We will see in about 2 years if I am wrong.
YMMV
Yes but overall SM still delivers the best overall usability package for me.
Not for everyone or course. Use Google or facebook extensively and you are
probably better off with a Chromium based browser. But the good thing is you
can run bioth side by side if needed :)
FRG
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
