Crashing After Update

[Eakamai]

Just upgraded from v. 2.53.11 which worked perfectly, to v.2.53.13 and now it's crashing.
For some reason I am unable to send the report directly, so I will give info here.

Using Frank's msg as a template (What info to give if having a problem...):
#0.5. What version of SeaMonkey are you are using? If you are also spoofing your UA (useragent) ...
-- 2.53.13 - NO UA SPOOFING

#1. What happened in SafeMode?
-- SAME PROBLEM/SAME ERROR

#2. What happened when you tried a new, clean, additional profile?
-- SAME PROBLEM/SAME ERROR

#3. Name of theme (if any) in use at the time of the issue.
-- N/A

#4. List of (if any) all extensions:
-- AMO Browsing for SeaMonkey 0.10.0
ChatZilla 0.13
Cookies Exterminator 2.9.4
DOM Inspector 2.0.19
Don't Fuck With Paste 2.3.1
Double Click Closes Tab [converted] 0.27.1-signed.1-signed
Greasemonkey [converted] 3.17
Image Zoom 0.6.3.1-signed.1-signed
Lightning 5.8.13
NetVideoHunter 1.20
NoScript 5.1.9
NoSquint for SeaMonkey 2.1.11
Remove Duplicate Messages (Alternate) 0.3.15
Speed Dial 0.9.6.18
uBlock Origin 1.16.4.30

#5, #6, #7, #8, #10 ARE ALL 'N/A'

#9. State how much RAM your PC has, especially with memory type issues.
-- 8 GB (however, I multiboot various systems and this one is only 32bit).
-------------------------------------------------------------------------
DETAILS
AvailablePageFile: 6013710336
AvailablePhysicalMemory: 2337112064
AvailableVirtualMemory: 1874157568
BlockedDllList:
BreakpadReserveAddress: 110559232
BreakpadReserveSize: 83886080
BuildID: 20220704152543
CPUMicrocodeVersion: 0xba
CrashTime: 1664167968
Email:
InstallTime: 1663874147
MozCrashReason: js::jit::InitProcessExecutableMemory() failed
ProductID: {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
ProductName: SeaMonkey
ReleaseChannel: release
SafeMode: 1
SecondsSinceLastCrash: 1774
StartupCrash: 1
StartupTime: 1664167968
SystemMemoryUsePercentage: 37
ThreadIdNameMapping: 1004:"Gecko_IOThread",
Throttleable: 1
TotalPageFile: 7479414784
TotalPhysicalMemory: 3740585984
TotalVirtualMemory: 2147352576
URL:
UptimeTS: .5728769
Vendor: Mozilla
Version: 2.53.13
This report also contains technical information about the state of the application when it crashed.
====================================================
QUESTIONS:
I've never had a problem with mozilla mail or Seamonkey, so I've never had to uninstall it. I've always upgraded.
I was going to uninstall/re-install (using Revo). Will it delete the mail folders (they are in a custom location)?
Of course they are backed up & I can direct Revo to ignore.... I wonder if normal uninstall leaves mail storage alone?

OR, can I simply install older version OVER this newest one? Usually this spells trouble for windoze progs.
--------------------------------------------------------------------------
Thank you very much for any help!

[frg]

So about 2GB reserved for the vm
AvailablePhysicalMemory: 2337112064

Indicates it is running out of memory:
MozCrashReason: js::jit::InitProcessExecutableMemory() failed

Try a new test profile and/or give the vm 3GB. 2GB should work initially but not sure what is still running in the vm and/or how it is set up. 2.53.13 needs a bit more memory because of backports allowing complex sites to render correctly. You can also try toe 2.53.14 beta. Final is a few days away and has only 3 minor fixes in over the beta.

FRG

[Frank Lion]

Just upgraded from v. 2.53.11 which worked perfectly, to v.2.53.13 and now it's crashing....


....QUESTIONS:
I've never had a problem with mozilla mail or Seamonkey, so I've never had to uninstall it. I've always upgraded.
I was going to uninstall/re-install (using Revo). Will it delete the mail folders (they are in a custom location)?
Of course they are backed up & I can direct Revo to ignore.... I wonder if normal uninstall leaves mail storage alone?

OR, can I simply install older version OVER this newest one? Usually this spells trouble for windoze progs.
--------------------------------------------------------------------------

Thanks for the info. There have been just a couple of 2.53.13 crashes reported here and they seem to be memory related (like yours). But only 2GB RAM on a VM, if that's what you're using, is pushing it, RAM-wise.

I suggest you go back to 2.53.11 for a short while and then later try the release version of 2.53.14, as not everyone wants to test beta versions.

#1.Back up the whole Mozilla folder in C:\Users\whatever\AppData\Roaming\ and that different location Mail folder.

#2. Uninstall 2.53.13 using the Windows uninstaller and say NO to any 'remove all data?' type prompt. Then just install 2.53.11 as you normally would and all should be how you left it.

In practice, you can safely go backwards and forwards with these releases and I have done this (2.49.x > 2.53.0 and back being the last one you couldn't, profile-wise.) Just be aware that 2.53.15 will be the next one that will mess up your profile if you go backwards and forwards. But that's a while away.

But, 2.53.13 back to 2.53.11 is fine, well, as fine as anything can be.

[frg]

2.53.15 and back is only minor. Locale setting in prefs will be reset.

Clear private data prefs were changed in 2.53.9 so I don't think anything bad will happen going back. to 2.53.11. But take a backup in any case.

The recent betas are usually more like release candidates. .14b1 is no exception. If you have problems with it you will have problemes with the GA.
I tested 2.53.14 in a ubuntu 14.04.6 vm with 2GB and it started fine. ymmv.

FRG

[Eakamai]

So about 2GB reserved for the vm
AvailablePhysicalMemory: 2337112064

Indicates it is running out of memory:
MozCrashReason: js::jit::InitProcessExecutableMemory() failed

Try a new test profile and/or give the vm 3GB. 2GB should work initially but not sure what is still running in the vm and/or how it is set up. 2.53.13 needs a bit more memory because of backports allowing complex sites to render correctly. You can also try toe 2.53.14 beta. Final is a few days away and has only 3 minor fixes in over the beta.

FRG

That's the first thing I noted. No vm, but a very old rescued sff business system (32bit/4gb). Your explanation of the newer release was fantastic.
Just what I had suspected. Can't wait to upgrade and test newer version.

Thank you!

[Eakamai]

Thanks for the info. There have been just a couple of 2.53.13 crashes reported here and they seem to be memory related (like yours). But only 2GB RAM on a VM, if that's what you're using, is pushing it, RAM-wise.

I suggest you go back to 2.53.11 for a short while and then later try the release version of 2.53.14, as not everyone wants to test beta versions.

But, 2.53.13 back to 2.53.11 is fine, well, as fine as anything can be.

Thanks very much Frank! It worked a Charm. As I mentioned above, can't wait to upgrade & test newest versions.

[Frank Lion]

Thanks very much Frank! It worked a Charm.

No problem.

The release version of 2.53.14 is (already!) out, so I suggest you give your OS a Defrag and Disk Check to improve how its handling things and then give this new version a go in a week or so.

In the unlikely event of you having the same crashing problem in that, at least now you know how easy it is to go back!

Note: I've only glanced at this, but it might be worth reading - https://answers.microsoft.com/en-us/win ... 407e7699cc

[Stereodoc]

Eakamai, I had a similar problem as yourself. I tried a bunch of different things. I ended up replacing an old PC because of insufficient memory.

viewtopic.php?f=40&t=3097528