NFN Smith wrote:
Don Spam's Reckless Son wrote:
I find 2.53.x levels slower than 2.49.x levels, but - as you say -
compatible with more websites. My 2.53.5 has an unfortunate tendency
to lock up one of my processors if I visit certain websites. The only
way out is to quit the program, restart and then "Restore Previous
Session". Of course I lose my "Private Browsing" session.
I'm having good performance with 2.53.* In 2.49.x (and several versions
before that, and I don't remember how far), I had problems, where if I
leave Seamonkey open overnight, the next morning, there's a lot of
sluggishness, and where active memory usage is often in excess of a GB.
Sometimes I was seeing as much as 1.5 GB, and I think I've seen nearly 2
GB once or twice.
However, with 2.53.* those problems are considerably less. Leaving
Seamonkey open overnight, I rarely see too much above a GB, and even
then, performance degradation is much less. Before, 2.53, a restart was
essential. Since 2.53, a restart isn't a bad idea, but by the same
token, Seamonkey isn't unusable, either.
For years (I'm up to 2.53.6), I've seen memory usage creep upward as
long as the program is running, and it often reaches two or three GB,
sometimes even four, if I watch streaming videos. It doesn't seem to
matter where I watch them; SM never releases the memory when it's done.
My cache is set to "let SeaMonkey manage" it, but clearing it doesn't
release the memory either. Same for "clear private data" -- SM acts as
if it's forgotten all that stuff, but Windows Task Manager shows the RAM
still in use and allocated to SM. The only way to free memory is to
close the program and restart it.
Does that count as a "memory leak" in the traditional sense of the term?
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
