Hi. While I daily drive FreeBSD, a machine I use very frequently runs
the 32bit build of Windows 10 21H2. I have been using a pretty old (~1-2
years, not sure the version) build of SeaMonkey on it, and it was
working okay. But after the update to 2.53.17 it started to randomly
crash, and 2.53.18 beta also has the same issue.

Now, I think I heard this is already known somewhere and it is not being
fixed due to the lack of users. But SeaMonkey is a crucial part of my
workflow, even if it'll get discontinued in the near future I hope this
can be fixed for now. I tried running seamonkey from cmd (as I get
stdout on *nix) but I don't seem to get any output. What's a good way to
get the logs that could potentially be reported and help fix this issue?

Best regards,
Yuchan Seo

Yuchan Seo wrote:

> a machine I use very frequently runs
> the 32bit build of Windows 10 21H2.

Any reason to not update to Win10 22H2? (that's the final 'major' update
to Win10, after which it will only receive monthly 'minor' fixes).

Andy Burns wrote:
> Yuchan Seo wrote:
>
>> a machine I use very frequently runs
>> the 32bit build of Windows 10 21H2.
>
> Any reason to not update to Win10 22H2? (that's the final 'major' update
> to Win10, after which it will only receive monthly 'minor' fixes).
What I'm actually running is Windows 10 Enterprise IoT LTSC 21H2, a
version of Windows 10 originally intended to be used on enterprise
machines, and so it has 10 years of support date (ends ~2032 or so) and
doesn't have much of the 'crapware's like Candy Crush (lol).

So I just tried installing the latest 2.53.18 32bit build on a machine
running Windows 10 21H1 x64 (not my machine, borrowed) and the same
crashes doesn't seem to happen here.

Does anyone else have more knowledge about this problem? I don't have
many Windows machines so my testing is pretty limited.

Yuchan Seo <hexagonwin@disroot.org> writes:

> So I just tried installing the latest 2.53.18 32bit build on a machine
> running Windows 10 21H1 x64 (not my machine, borrowed) and the same
> crashes doesn't seem to happen here.
>
> Does anyone else have more knowledge about this problem? I don't have
> many Windows machines so my testing is pretty limited.

Does it crash with a new profile, or in safe mode?

Yuchan Seo wrote:
> Andy Burns wrote:
>> Yuchan Seo wrote:
>>
>>> a machine I use very frequently runs
>>> the 32bit build of Windows 10 21H2.
>>
>> Any reason to not update to Win10 22H2? (that's the final 'major' update
>> to Win10, after which it will only receive monthly 'minor' fixes).
> What I'm actually running is Windows 10 Enterprise IoT LTSC 21H2, a
> version of Windows 10 originally intended to be used on enterprise
> machines, and so it has 10 years of support date (ends ~2032 or so) and
> doesn't have much of the 'crapware's like Candy Crush (lol).
>

Still if you have a key you should run the x64 version. Unless you have some
expensive special hardware with x86 drivers only there is just no use case for
Windows x86 in any flavor left. Anything post 2008 with 4 GB should be able to
run the x64 version and keys work for both. Usually you run into an OOM with
x86 more or less fast these days.

I thest new versions only in a vm under 7 or 8.1 x86 these days. Test means
they start and run for a few minutes.

If you have a crash report from the official 2.53.18b1 beta I can take a look
but what I saw in the last days was mostly OOMs. Some macOS crashes I plan to
take a look into but Windows x86 is just not something high on the priority list.

Might lso want to turn off hardware acceleration if you use an AMD or Nivdia
card. All x86 driver from them are more or less buggy. Intel is usually
horrible but x86 is hit and miss compared to the others.

FRG

Richmond wrote:
> Yuchan Seo <hexagonwin@disroot.org> writes:
>
>> So I just tried installing the latest 2.53.18 32bit build on a machine
>> running Windows 10 21H1 x64 (not my machine, borrowed) and the same
>> crashes doesn't seem to happen here.
>>
>> Does anyone else have more knowledge about this problem? I don't have
>> many Windows machines so my testing is pretty limited.
>
> Does it crash with a new profile, or in safe mode?
>

He's saying it doesn't crash.

frg wrote:
> Anything post 2008 with 4GB should be able to run the x64 version and> keys work for both.You're right, but in this case my machine is from
2019 with 2GB of ram and Intel made some stupid limitations on Atom
devices so they only run 32bit EFI despite having proper 64bit processor.

> If you have a crash report from the official 2.53.18b1 beta I can take a
> look but what I saw in the last days was mostly OOMs. Some macOS crashes
> I plan to take a look into but Windows x86 is just not something high on
> the priority list.
I understand there are not many users on win32 anymore and it's not a
high priority. I'll try sending a crash report from 2.53.18b1 though.

Yuchan Seo wrote:
> frg wrote:
>> Anything post 2008 with 4GB should be able to run the x64 version and> keys work for both.You're right, but in this case my machine is from
> 2019 with 2GB of ram and Intel made some stupid limitations on Atom
> devices so they only run 32bit EFI despite having proper 64bit processor.

2GB is not enough for todays websites. You run into an OOM fast. I also needed
to adjust the stack size for the Windows builds to avoid some crashes on web
sites with complex html and/or css. The adds to the ram requirements too. The
atom is a joke and was only good for actual iot devices like nas systems with
Linux.

Buy a used system with 8GB and be happy. My latest Thinkpad T430s and X230
laptops run Server 2019 happy with 8GB and support available till 2029.

>
>> If you have a crash report from the official 2.53.18b1 beta I can take a
>> look but what I saw in the last days was mostly OOMs. Some macOS crashes
>> I plan to take a look into but Windows x86 is just not something high on
>> the priority list.
> I understand there are not many users on win32 anymore and it's not a
> high priority. I'll try sending a crash report from 2.53.18b1 though.
>

With 2GB of memory I can tell you the outcome. Use uBlock and NoScript will
only help so much. Without it it is game over fast.

FRG

Yuchan Seo wrote on 19/11/23 11:02 pm:

<Snip>

> I understand there are not many users on win32 anymore and it's not a
> high priority. I'll try sending a crash report from 2.53.18b1 though.
>
Pick me!! This 64bit HP Laptop had Win7 WOW 32bit pre-installed on it
when I brought it, second hand, in 2009.

I've since installed 64bit Linux on it (Dual Boot) but would like to
keep my win32 running as long as possible.
--
Daniel

Daniel65 wrote:
> Yuchan Seo wrote on 19/11/23 11:02 pm:
>
> <Snip>
>
>> I understand there are not many users on win32 anymore and it's not a
>> high priority. I'll try sending a crash report from 2.53.18b1 though.
>>
> Pick me!! This 64bit HP Laptop had Win7 WOW 32bit pre-installed on it when I
> brought it, second hand, in 2009.
>
> I've since installed 64bit Linux on it (Dual Boot) but would like to keep my
> win32 running as long as possible.

Grab the x64 and replace x86 with x64. Yes I know means to reinstall programs.
Check the key. Probably has an slic 2.1 in the bios so you can activate easy.
If not pick at least Win 7 x64 Pro.

FRG

frg wrote on 20/11/23 9:04 pm:
> Daniel65 wrote:
>> Yuchan Seo wrote on 19/11/23 11:02 pm:
>>
>> <Snip>
>>
>>> I understand there are not many users on win32 anymore and it's not a
>>> high priority. I'll try sending a crash report from 2.53.18b1 though.
>>>
>> Pick me!! This 64bit HP Laptop had Win7 WOW 32bit pre-installed on it
>> when I brought it, second hand, in 2009.
>>
>> I've since installed 64bit Linux on it (Dual Boot) but would like to
>> keep my win32 running as long as possible.
>
> Grab the x64 and replace x86 with x64. Yes I know means to reinstall
> programs.
> Check the key. Probably has an slic 2.1 in the bios so you can activate
> easy. If not pick at least Win 7 x64 Pro.
>
> FRG

You haven't been talking to my sister have you, FRG!!

I mean this (What??) 16 year old Lap Top .... The Scratch-pad-thingee
doesn't work, so I've got an external Mouse on a cable. and I've spilt
Cola on the keyboard, so I've got an external keyboard.

(Have you heard the story about the guy who has had the same axe for
fifty years?? Sure, he's replaced the axe-head three times and the
handle has been replaced about a dozen times ..... but it's still the
same Axe!!)

My Laptop still works!! .... but my sister is hassling me to get a new
Laptop!!

One Day!! One Day!
--
Daniel

frg wrote:
> 2GB is not enough for todays websites. You run into an OOM fast. I also
> needed to adjust the stack size for the Windows builds to avoid some
> crashes on web sites with complex html and/or css. The adds to the ram
> requirements too. The atom is a joke and was only good for actual iot
> devices like nas systems with Linux.
I understand.. but my Win10 installation is very trimmed down, it runs
just fine now and currently I'm using the latest ungoogled chromium and
some Palemoon-based SM 2.49.5 fork. Not really what I wanted to use but
it works..
On idle I usually consume about 800MB ram, I don't think it's that bad
though? The stock Win10 install is way bloated, but I'm running Blackbox
instead of explorer.exe and also have most useless services disabled.

> Buy a used system with 8GB and be happy. My latest Thinkpad T430s and
> X230 laptops run Server 2019 happy with 8GB and support available till
> 2029.
I'm planning to do this in the long term, gonna buy something like a T430.