On 07/08/14 11:59, Trane Francks wrote:
On 8/6/14 9:36 PM, Daniel wrote:
On 06/08/14 22:10, Trane Francks wrote:
On 8/6/14 8:57 PM, Daniel wrote:
On 06/08/14 18:20, Big Jim wrote:
This has been driving me crazy for weeks. I apparently have the same
problem as Ben has. SM crashes several times a day without
warning. The
only symptom that I can see is that, according to Task Manager with
about 20 tabs open, memory use steadily increases even if the computer
is idle. At about 2,000,000K memory use SM starts to slow down and
act
funky. Somewhere in the vicinity of 2,500,000K+ SM abruptly shuts
down.
I am running Windows 7 64bit and have 16 gig of installed memory, so
memory use should not be a problem. I never had a problem before this
release of SM even with several dozen tabs open.
Big Jim, I notice you are running "Mozilla/5.0 (Windows NT 6.1; WOW64;
rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26.1".
WOW64 is a (sort of) 32bit OS, isn't it?? So is limited to 4GB RAM with
file size limited to 2GB, isn't it??
So, if SM is using 2.0GB or 2.5GB, it should be shutting down
shouldn't it??
No, why would it? Modern operating systems use virtual memory. In the
case of a Windows system with 4GB RAM, the virtual page file will
default to 4GB, which means the system can access a total of 8GB
combined virtual and physical memory.
If they have a virtual memory set, yes, but maybe they have Virtual
memory set to zero. Who knows?!?!
If that were the case, Windows would warn the user that it was nearly
out of resources and to close one or more applications prior to
SeaMonkey being able to crash.
O.K.
--
Daniel
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101
Firefox/29.0 SeaMonkey/2.26 Build identifier: 20140415200419
or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101
SeaMonkey/2.26 Build identifier: 20140408191805
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
