On 05/18/09 18:52, rafe wrote:
> yes, I have the same sorts of problems -- very often when I return to
> the computer, SeaMonkey 1.1.13 has somehow hung and I have to press
> Ctrl-Esc numerous times to get the hanging app-dismiss screen to wake
> up Doodle's Screen Saver and turn the monitor on.
>
> it certainly has the feel of a memory leak -- after 2-3 days
> frequently everything else running grinds down to a virtual halt& I
> can hear lots of swapping. if closing and restarting SM doesn't fix
> it, I am obliged to reboot.
There are no memory leaks, at least none of this size in Mozilla. Debug
builds have built-in checks that would show leaks immediately. (That's
how I know of one that leaks a few bytes but I don't know how to find
that.) As have said every time this "leak" discussion starts again, this
is most likely due to a non-optimal implementation of the C-library heap.
Especially, if a SM restart doesn't clear the problem then it is
unlikely to be Mozilla problem...
But why keep a system running for days anyway? If it's a server, don't
run browsers on it. If it's a desktop/workstation then switch it off
when the work is done. What a waste of energy. I cannot leave mine
running for more than a day anyway. So discuss all you want, I won't be
able to reproduce, let alone fix it. ;-)
--
Please Enhanced OS/2 builds of Mozilla applications
reply in
http://pmw-warpzilla.sf.net/newsgroup
Steve's Warpzilla Tips:
http://www.os2bbs.com/os2news/Warpzilla.html_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2