On 15/03/15 07:25, Eric wrote:
Daniel wrote:
On 14/03/15 11:26, Eric wrote:
Has anyone else been experiencing Seamonkey Crashing after updating?

I've had to revert the other computer that I use for business purposes
to an older release of Seamonkey.  The other OS is Windows 7 Home
Premium 64 bit.

Here is what I've done to try and fix the crash problem.

On update, I'll do a warm boot of the system.  Crash.

Download and instal latest release of Seamonkey. Crash

warm boot.  Crash.

Revert to an older version 2.3.1. Crash.

warm boot.  Works.

I'm at my wits end with the crashes on the windows 7 machine.

This doesn't happen on my Vista Machine that I'm currently writing
this on.

Any ideas?

TIA

Eric

Eric, after you've had a crash, and you get an old version of SM
running, can you enter "about:crashes" (without the quotes) in the
address line and report back what is shown??

What would you like to see from it, pretty extensive file.  The only
thing that I saw that was interesting was about Last Pass, but nothing
specific about Last Pass.

Several tabs come up available that have a lot of different info.

Let me know what you want to see and I will do my best to provide it.

Eric

Eric, the stuff from about:crashes is gobbledegook to me but it may mean something to others here-abouts, so post the last few lines (top) of it here and, hopefully, someone here will know what to do with it.

Additionally, I notice you mentioned "Last Pass" as being problematic in one of your other posts. Go to Tools->Add-on Manager and disable Last Pass and then completely close and re-start SeaMonkey and see if it behaves better.

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 SeaMonkey/2.32 Build identifier: 20141218225909
or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 SeaMonkey/2.33 Build identifier: 20150215202114
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to