Hello again!
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
Is it because it can't be determined when SM is hogging about almost 2
GB of RAM + 1.6 GB of VM (heavy user with over/about 150 tabs from two
windows)? I remember it used to be able to know what was causing the
crashes, but lately not anymore. All of my other softwares and OS do not
crash. Just SM. :(
Thank you in advance. :)
--
"Did the ant fall off the toilet seat because she was pissed off?" --unknown
/\___/\ 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
