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. 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.
--
"Even an ant can hurt an elephant." --Proverb
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
