MozillaZine

Seamonkey 2.49.5 APPCRASH

User Help for Seamonkey and Mozilla Suite
Drikuz
 
Posts: 2
Joined: September 6th, 2019, 8:00 am

Post Posted September 6th, 2019, 8:09 am

Hi. I am a long time user, since the time of Netscape Communicator.

I uninstalled Seamonkey 2.49.4 32-bit and installed 2.49.5 64-bit.
Unfortunate it crashes on start and I had to reinstall 2.49.4.

Code: Select all
Problem signature:
Problem Event Name:   APPCRASH
Application Name:   seamonkey.exe
Application Version:   52.9.1.7155
Application Timestamp:   5d47510b
Fault Module Name:   StackHash_d65d
Fault Module Version:   0.0.0.0
Fault Module Timestamp:   00000000
Exception Code:   c0000005
Exception Offset:   000000006fff0d2a
OS Version:   6.1.7601.2.1.0.256.48
Locale ID:   1043
Additional Information 1:   d65d
Additional Information 2:   d65dbab503f5b6e6a9b6f6bb92e03621
Additional Information 3:   5e73
Additional Information 4:   5e73314ff177f89621efd6a85c965f92

Frank Lion

User avatar
 
Posts: 20472
Joined: April 23rd, 2004, 6:59 pm
Location: ... The Exorcist....United Kingdom

Post Posted September 6th, 2019, 10:25 am

Drikuz wrote:and installed 2.49.5 64-bit

Just install the 2.49.5 32 bit instead, it works fine on Windows 7.

I tested 64 bit Firefox in the past and could never find any noticeable advantage to it.
Metal Lion latest SeaMonkey & Thunderbird Themes - Sea Monkey and Silver Sea Monkey
"The only thing necessary for the triumph of evil, is for good men to do nothing." - Edmund Burke (attrib.)

Drikuz
 
Posts: 2
Joined: September 6th, 2019, 8:00 am

Post Posted September 6th, 2019, 12:00 pm

Ok, installed the X86 version and this works. Strange, I changed a lot open source programs to a X64 version over the years and never had a problem but... solved for now!

kerft
 
Posts: 502
Joined: January 30th, 2019, 9:38 am

Post Posted September 6th, 2019, 12:36 pm

Possibly the 64-bit would work if you did a profile backup, then uninstalled and cleaned up emptying all Seamonkey stuff, then reinstall, then if it works attempt to restore profile. If that causes the crash, then "selectively" create a new profile using one bit of your profile at a time unless one causes the crash. Or just continue with the 32-bit.

frg
 
Posts: 803
Joined: December 15th, 2015, 1:20 pm

Post Posted September 7th, 2019, 3:52 am

I am running private x64 builds since around 2.40. The only problem which remained until recently was the MAPI crash when sending emails from an external application. If the x64 crashes on start you probably have an external problem either hardware or software related. In most crashes I saw so far ancient graphics drivers, really old add-ons or virus scanners seem to at least be present and might have caused it.

Bac_a_sable
 
Posts: 25
Joined: January 1st, 2017, 12:35 pm
Location: Near Lyon / France in Europe

Post Posted September 7th, 2019, 5:17 am

I just install 2.49.5 64 bit at same place of "old" 2.49.4 32 bit without remove this version before (thing that should never be done) and surprisingly all works fine here.
Seamonkey seems robust :)
I install 2.49.5 64 bit at work but with clean installation (can not "play" in this configuration): all is also fine.

Both w10 pro.

frg
 
Posts: 803
Joined: December 15th, 2015, 1:20 pm

Post Posted September 7th, 2019, 9:53 am

> just install 2.49.5 64 bit at same place of "old" 2.49.4 32 bit without remove this version before (thing that should never be done) and surprisingly all works fine here.

You now should have 2 SeaMonkey entries in your "Programs and Features" dialog. One old and one new. Please uninstall both and reinstall the x64. The x64 resides in "Program Files". The x86 in "Program Files (x86)".

LordOfTheBored
 
Posts: 296
Joined: December 7th, 2005, 8:36 pm

Post Posted September 7th, 2019, 6:27 pm

Bac_a_sable wrote:I just install 2.49.5 64 bit at same place of "old" 2.49.4 32 bit without remove this version before (thing that should never be done) and surprisingly all works fine here.
Seamonkey seems robust :)
I install 2.49.5 64 bit at work but with clean installation (can not "play" in this configuration): all is also fine.

Both w10 pro.

I don't know about other interactions this configuration will have, but I see a potential risk to your user profile here.

The 32-bit version will continue to exist, and continue to be operational should it be found and invoked. If you don't continue to update it, and forget it is there, it will grow increasingly out of sync with the 64-bit version.
Some day in the future, you might accidentally open the outdated 32-bit version, and it will not know how to handle the user profile from the newer version you've been using. There's a not-insignificant potential for data corruption here.

Please take frg's advice. Your bookmarks thank you, your e-mails thank you, and your news feeds thank you.

frg
 
Posts: 803
Joined: December 15th, 2015, 1:20 pm

Post Posted September 8th, 2019, 2:17 am

> I don't know about other interactions this configuration will have, but I see a potential risk to your user profile here.

It is basically a mess not uninstalling it before. Goes the other way round too if you want to use x86. I didn't put "uninstall it first" in the release notes just for fun.

FRG

therube

User avatar
 
Posts: 20046
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Post Posted September 8th, 2019, 4:12 am

@Drikuz, did you get an actual crash in SeaMonkey?
If so, its' URL (in about:crashes)?

StackHash_0a9e may be DEP related. (Note: differing suffix.)
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript

Bac_a_sable
 
Posts: 25
Joined: January 1st, 2017, 12:35 pm
Location: Near Lyon / France in Europe

Post Posted September 8th, 2019, 7:35 am

frg wrote:> just install 2.49.5 64 bit at same place of "old" 2.49.4 32 bit without remove this version before (thing that should never be done) and surprisingly all works fine here.

You now should have 2 SeaMonkey entries in your "Programs and Features" dialog. One old and one new. Please uninstall both and reinstall the x64. The x64 resides in "Program Files". The x86 in "Program Files (x86)".

Well, x86 was already located in "Program Files (x86)" (E: drive, not C: drive; i "preserve C: space as much as i can)
Noting related to Seamonkey located on "Program Files" in this computer :).
OK, i will do it "properly and return here to tell if all still ok (hope so!)

Bac_a_sable
 
Posts: 25
Joined: January 1st, 2017, 12:35 pm
Location: Near Lyon / France in Europe

Post Posted September 8th, 2019, 7:43 am

Done: removed and re install at same place (was empty between: i verify :) )

Works as it have always work.... fine!

Note: default location proposed ios not "x86" directory; i have to force it:
Default proposed by installer was "C:\Program Files\Seamonkey" ans i use "E:\Program Files (x86)\Seamonkey" instead.
Installer is seamonkey-2.49.5.installer.exe and the 64 bits version.
User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.5

frg
 
Posts: 803
Joined: December 15th, 2015, 1:20 pm

Post Posted September 8th, 2019, 2:16 pm

> Default proposed by installer was "C:\Program Files\Seamonkey" ans i use "E:\Program Files (x86)\Seamonkey" instead.

Convention is that x86 (32-bit) only uses "Program Files (x86)". For c: it should not be changed. E: is non-standard anyway so doesn't matter.

I never bothered to move programs to a different directory on Windows. If c: gets damaged you usually loose the registry and it is either restore or reinstall time anyway. Might help with some malware expecting to find something in the default location and fails then but that is it mostly.

FRG

Return to SeaMonkey Support


Who is online

Users browsing this forum: No registered users and 1 guest