Seamonkey fails to run

User Help for Seamonkey and Mozilla Suite
Post Reply
danlcarr
Posts: 2
Joined: May 2nd, 2023, 12:40 pm

Seamonkey fails to run

Post by danlcarr »

Hi everyone,
Seamonkey fails to run after install or upgrade from 2.53.12 to

Does this for Seamonkey 2.53.13, 2.53.14, 2.53.15, 2.53.16

Windows 7 32-bit

AvailablePageFile: 5686222848
AvailablePhysicalMemory: 1909784576
AvailableVirtualMemory: 1940647936
BlockedDllList:
BreakpadReserveAddress: 40566784
BreakpadReserveSize: 83886080
BuildID: 20230320084237
CPUMicrocodeVersion: 0x25
CrashTime: 1681271059
InstallTime: 1681271059
MozCrashReason: js::jit::InitProcessExecutableMemory() failed
ProductID: {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
ProductName: SeaMonkey
ReleaseChannel: release
SafeMode: 0
SecondsSinceLastCrash: 1326711
StartupCrash: 1
StartupTime: 1681271059
SystemMemoryUsePercentage: 45
ThreadIdNameMapping: 2000:"Gecko_IOThread",
Throttleable: 1
TotalPageFile: 6954643456
TotalPhysicalMemory: 3478179840
TotalVirtualMemory: 2147352576
URL:
UptimeTS: 1.17800163
Vendor: Mozilla
Version: 2.53.16

This report also contains technical information about the state of the application when it crashed.
v_v
Posts: 157
Joined: September 18th, 2021, 8:57 am

Re: Seamonkey fails to run

Post by v_v »

Danlcarr,

Did you use the "Windows x86" version of SeaMonkey from " https://www.seamonkey-project.org/releases/#2.53.16 "?

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

Re: Seamonkey fails to run

Post by frg »

https://bugzilla.mozilla.org/show_bug.cgi?id=1792877

is open for this. I doubt it will be fixed. Works fine for me in a Windows 7 x86 vm and on the last laptop I treied which still had an x86 version. If you really must use x86 make sure your are on the latest service pack and all updates installed including the sha-2 support fix. Might be the clang compiler used. You can try the unofficial version which uses a different one: https://www.wg9s.com/comm-253/

The people who wrote in the bug never did give much information about used hardware. The first one uses a NVS160M which indicates a system with a buggy gfx driver and a chip which might become defective any time because of the Nvidia bug. Both systems where this was reported against should be capable of running Windows 7 x64.

If I have my way official x86 support will be discontinued in one of the next releases. Year is 2023 not 2008. Windows 7 x64 support will not be discontinued. We are not google but also not museum curators.

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

Re: Seamonkey fails to run

Post by therube »

Oh, no clue about this, but... if you're into hacking...
MozCrashReason: js::jit::
InitProcessExecutableMemory() failed
https://www.google.com/search?q=%22Init ... irloom-srp..

There are a few "jit" prefs.

Code: Select all

javascript.options.baselinejit
javascript.options.wasm_baselinejit
javascript.options.wasm_ionjit
By default, they are all true.
You might try toggling them to false (in about:config) & see if that makes any difference?

Do this on a COPY of your existing Profile.
Run .12 in that COPY.
Toggle those Prefs, in that COPY.

Then try running the current release - using that COPY as its' Profile Folder.


Again, no clue whether it will have any bearing on the matter, but relatively easy to test it out, maybe.
(Just make sure you do this on a COPY, & you run the relevant versions of SeaMonkey on that COPY.)
Fire 750, bring back 250.
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
danlcarr
Posts: 2
Joined: May 2nd, 2023, 12:40 pm

Re: Seamonkey fails to run

Post by danlcarr »

I used the "Windows x86" version of SeaMonkey from " https://www.seamonkey-project.org/releases/#2.53.16 "?
failed

also tried removed Seamonkey and profile data, installed Seamonkey 2.53.16
failed again.

What version of Java is needed?

Windows 7 32-bat 8GB ram

error log

AvailablePageFile: 5976477696
AvailablePhysicalMemory: 2491244544
AvailableVirtualMemory: 1940647936
BlockedDllList:
BreakpadReserveAddress: 39649280
BreakpadReserveSize: 83886080
BuildID: 20230320084237
CPUMicrocodeVersion: 0x25
CrashTime: 1684532551
InstallTime: 1684532341
MozCrashReason: js::jit::InitProcessExecutableMemory() failed
ProductID: {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
ProductName: SeaMonkey
ReleaseChannel: release
SafeMode: 0
SecondsSinceLastCrash: 210
StartupCrash: 1
StartupTime: 1684532551
SystemMemoryUsePercentage: 28
ThreadIdNameMapping: 5844:"Gecko_IOThread",
Throttleable: 1
TotalPageFile: 6954643456
TotalPhysicalMemory: 3478179840
TotalVirtualMemory: 2147352576
URL:
UptimeTS: 2.355064081
Vendor: Mozilla
Version: 2.53.16

This report also contains technical information about the state of the application when it crashed.
TPR75
Posts: 1352
Joined: July 25th, 2011, 8:11 am
Location: Poland

Re: Seamonkey fails to run

Post by TPR75 »

danlcarr wrote:What version of Java is needed?
You don't need Java to install and run SeaMonkey. If SM refused to work after update from 2.53.13 to 2.53.16 then it could be some extension and/or theme conflict. It can happen when addons are outdated and no longer maintained by their authors.

If you can't install and run SeaMonkey on "clean" profile then it must some problem with OS (here:Windows 7 32-bit). Helping to solve such problem can be difficult.
--
frg
Posts: 1361
Joined: December 15th, 2015, 1:20 pm

Re: Seamonkey fails to run

Post by frg »

Well there is bug https://bugzilla.mozilla.org/show_bug.cgi?id=1792877

You can try Bills version https://www.wg9s.com/comm-253/

It seems started when I switched the builds to clang. The x86 msvc ones crashed under heavy load/media playback. Also enlarged some stack values to allow render some complex websites. Still works with Windows x86 in a vm. No bare metal left here running x86. Plenty of Windows 7 x64 ones which work fine.

In any case 8GB of memory means your system is more than capable of running Windows 7 x64. Update time. If I have my way the x86 versions will be offcially discontinued in one of the next releases anyway.

FRG
Post Reply