Ant wrote: > On 6/30/2013 3:59 AM PT, Noob42 typed: > >>> "SeaMonkey 2.17.1 Crash Report [@ EMPTY: no crashing thread identified; >>> corrupt dump ] >>> ... >>> "EMPTY: no crashing thread identified; corrupt dump ..." >>> >>> For an example of my latest crash report from a few minutes ago: >>> https://crash-stats.mozilla.com/report/index/bp-b5b35741-6423-4c74-a562-a30932130607 >> >> xpcom_runtime_abort(###!!! ABORT: OOM: file >> e:\builds\slave\rel-c-rel-w32-bld\build\mozilla\xpcom\string\src\nsTSubstring.cpp, >> line 533) >> >> You seem to have run out of virtual memory. >> Maybe try increasing the size of the Windows page file? >> How much memory is the Seamonkey process using right >> before the crash? > > I have seen my SM go high as 2 GB of "Mem Usage" and "VM Size" according > to my 32-bit Windows XP Pro. SP3's Task Manager.
I use Mark Russinovich's Process Explorer. http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx (Some of his tools are better than the native tools.) > My VM can go high as 8 GB of pagefile with 2.5 GB (actually 3, > but I think VRAM takes 512 MB of it?) of RAM. (VRAM takes virtual memory, not physical memory.) OK, so you don't have a problem with virtual memory. I think your problem is that Windows can't allocate more than 2 GB to a 32-bit process, unless you mess with the kernel config: http://msdn.microsoft.com/en-us/library/windows/desktop/aa366778%28v=vs.85%29.aspx (I have personally never played with IMAGE_FILE_LARGE_ADDRESS_AWARE.) Regards. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
