On 1/05/2017 10:00 PM, TCW wrote:
On Sat, 29 Apr 2017 00:32:39 +1000, Daniel <[email protected]>
wrote:
On 28/04/2017 8:25 PM, TCW wrote:
On Fri, 28 Apr 2017 15:45:05 +1000, Daniel <[email protected]>
wrote:
On 28/04/2017 4:21 AM, TCW wrote:
On 4/24/17 8:05 AM, TCW wrote:
Just saw it here
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
Well, after quiet a bit of regular browser use, I am up to 1.2GB of RAM
use on SM 2.51b with one window open.
While I would say that's a memory leak (even after running the options
under about:memory "Free Memory") it's certainly not as laggy as 2.50
was when it got to this RAM consumption level. Still seems performant to
me.
TCW, is it an activity thing or is it just growing?? i.e. if you find
out how much memory SM is using, then do nothing for some time
(overnight, maybe, or whilst you go for a meal), then when you comeback,
has the memory usage increased??
Seems to be related to activity. It doesn't seem to grow it just left
alone. Memory just isn't getting freed.
Which gets back to one of my hobby-horses .... why have buckets of
memory if it never gets used!!
Well, yes and no. This same mentality is why media rich (read:
bloated) web sites require a fast Internet connection and gobs of RAM
because they aren't designed for efficiency but because it's assumed
the user has gobs of RAM and system horsepower. No one designs apps to
be efficient, just chew up all that RAM CPU and all else be damned. No
one benefits from that mentality. Throwing more resources at the
problem never actually *fixes* the problem.
But if you have other programs that need that memory, then the system
(i.e. the OS, not any particular program) should be able to free up that
(used but now un-needed) memory .... but what would I know??
Not much, trust me! :-P
Right. People don't buy computers just to run a web browser. There
always other apps competing for memory+resources and one can make the
easy leap to the above stated argument that the other apps too are not
written for efficiency but to eat up as much resources as is possible.
Kinda sad when you think about it.
I think the Mozilla devs try hard to squash memory leaks (memshrink)
and improve performance (AWFY/AWSY) but most of the low hanging fruit
has already been picked. Better tools yet to be developed that will
more readily find memory leaks will help in this arena. Until then, we
keep reporting issues. =)
RGR!!
--
Daniel
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101
SeaMonkey/2.46 Build identifier: 20161213183751
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
