Dirk Munk wrote on 27/02/2019 13:34:
Gabriel wrote:
Dirk Munk wrote on 27/02/2019 10:53:
Frank-Rainer Grahl wrote:
Dear Frank-Rainer
This is *not* a bug!
It's very simple, if you open more tabs, you will need more memory. The
default memory setting simply is not sufficient for 'power users' with many
tabs open.
What I see here is what I've seen many times before. In a 32 bit environment,
memory constraints are very important, on OS level and application level. All
kinds of settings are done with the mindset of conserving memory.
When the OS or the application is moved to 64 bit, very often no one thinks
about removing memory constraints, so applications still run as if they were
32 bit applications. What should be done is checking all kind of memory
settings, and change these settings to let them use (much) more memory. After
all, that is the only purpose of 64 bit operating systems and applications,
make it possible to use more memory!
[cut]
Hello,
I really would like an official answer from the SM developers on this matter.
I followed your advice to increase the allocated RAM (on the previous thread
about it) to 4GB and *nothing* has ameliorate.
*But* I'm on macOS and I've always seen SM using a lot of RAM, really too much
for a (modern) browser that should load the tabs only when they are actually
in use. It should not matter if there are 150 tabs, but only 30 are loaded
because you are reading these websites.
SeaMonkey for macOS is already 64bit.
Still my SM 2.49.4 is hanging a lot of times a day, with CPU spikes to 90/100%
and the colored spinning wheel for 30 seconds. I observed this is happening
more often since I added a new news-server (astraweb).
Any clue?
Thank you.
It could have something to do with network settings in Seamonkey. For instance
there is a setting network.http.max-connections , you can try to increase it. I
have it at 512 at the moment.
In SM for macOS the default is already at 900!
There are many other of those kind of settings that I have increased over time
to remove restrictions. It seems you are running into some kind of restriction
somewhere, and now we have to figure out which one it is.
It would be useful to have a list with the details.
I now increased "network.http.max-persistent-connections-per-server" from 6 to
8.
I can't find a specific setting for the news-servers, but I also increasd
"network.websocket.max-connections" from 200 to 400.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
