Ken Rudolph wrote:
SeaMonkey has crashed 3 times in the past 3 hours and once last night. I've
gone several months without crashes; so this cluster comes out of the blue.
Win 10.0 17134
SM 2.49.1esr
Each has the same crash reason: EXCEPTION_ACCESS_VIOLATION_READ
There's lots more in the crash report that I think was automatically sent to
Mozilla. But I was wondering if anybody has an idea of what to do about this?
Latest version is 2.49.4. I would try this one first. Maybe a Windows 10
update has changed something. If the crashes persist please post a crash id.
FRG
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
