Ant wrote: > Is anyone else having problems with corrupted random rare crash dumps > from SeaMonkey (SM) v2.17.1 in a very old updated 32-bit Windows XP Pro. > SP3 machine (2.5 GB of RAM)? After my SM crashed, sent its crash reports > to Mozilla, restarted, and I did a about:crashes line to read the crash > reports. I see a lot of these lately: > > "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? Regards. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
