Lee wrote:
On 3/1/19, Paul B. Gallagher <[email protected]> wrote:
Lee wrote:
On 2/27/19, Paul B. Gallagher <[email protected]> wrote:
According to Task Manager, SM is using 1,051,192 KB of memory. Under
peak load, I would expect that to double; I haven't yet seen it reach 3
GB.
I did have some trouble this afternoon as I was perusing Google News.
For some stories, I clicked "View full coverage" and each time I did, SM
hung. As before, CPU peaked at 26–27% and RAM usage was a little over 2
GB. After two or three minutes, the cursor returned to its usual arrow
shape and CPU usage fell to under 10%. But the next time I clicked "View
full coverage," it was like standing on the brakes again.
Is this just with web pages open or do you also have mail and/or
newsgroups open at the time?
I always have Mail/News open.
<http://kb.mozillazine.org/Browser.cache.memory.capacity>
has a note that mail & newsgroups can be cached in memory, so if you
have a huge inbox or newsgroup maybe that's it?
I don't think I have "a huge inbox" -- definition? At the moment, 185
messages, 57 MB.
As for newsgroups, does this one count as huge? At the moment, three
unread of 109,466.
I don't know what you're doing that would cause
According to Task Manager, SM is using 1,051,192 KB of memory.
If you try closing mail & news what does task manager say then?
If I want to get there quickly, streaming videos. If not, I just have to
run it long enough and the RAM usage will gradually creep upward. I
suspect a memory leak -- closing a vid or its window has no effect on
RAM usage. Even closing the browser entirely, leaving only Mail/News,
doesn't change RAM usage. SM only releases RAM when the entire suite
terminates. I suppose that's because the cache survives until the
program terminates.
But I have noticed in recent years that when SM automatically polls and
downloads messages, everything else in the suite comes to a screeching
halt for a couple of seconds.
Yeah - not terribly surprising if SeaMonkey is single-threaded.
One thing you could try if you haven't already - set
browser.cache.memory.max_entry_size
to -1
https://developer.mozilla.org/en-US/docs/Mozilla/Preferences/Mozilla_networking_preferences
browser.cache.memory.max_entry_size 5120 (default)
-1 = no limit
The maximum size of an entry in the memory cache (in KB).
If you've got the memory cache size set to 4GB you should probably go
without a size limit on individual cache entries.
As noted upthread, I just increased it from the default to 1 GB, and I
have 8 GB of physical memory. SM's RAM usage seems to peak at 2 to 2.5
GB if I watch a lot of vids, but as noted above terminating and/or
closing those windows has no effect on RAM usage.
--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
