Pale Moon forum

just downloaded 31.41 and it crashes my windows 7

Hiya friend,

Any further pointers as to what was behind this, anything I can throw at it, run in the background, pages to load?

xul.dll is the culprit.
If I copy the version from the older release it works OK, but I don't know what other effect that would have.
I'll see if I can capture any more info about exactly what is happening.
I'm on Windows 7 Home premium up to date.

32-bit or 64-bit?

And what are the exact steps for us to try to reproduce the crash?

32bit Just trying to load Palemoon.
Here's the messages.
Problem signature:
Problem Event Name: APPCRASH
Application Name: palemoon.exe
Application Version: 5.2.1.8360
Application Timestamp: 637be41f
Fault Module Name: xul.dll
Fault Module Version: 5.2.1.8365
Fault Module Timestamp: 63827617
Exception Code: c000001d
Exception Offset: 008e21d5
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

As I said, if I replace it with the version of that module from 21/11/22 which is about 13k smaller, it works ok
I'll try just opening PM with just one pane and a few other things to see if it makes any difference.

Hmmmmmmmm, fascinating. I have PM 31.4.1 running on a 32-bit Win 7 Home Premium system with no obvious problems, but I haven't stress-tested it. PM certainly loads just fine, though.

Moonchild might need you to run AppCrashView and post the details from that for further troubleshooting.

Btw it's not a good idea to replace the xul.dll from one that is an older version because that's where most of the XUL platform stuff is built in.

0xc000001d (the crash exception code) normally means you're trying to run Pale Moon on hardware/CPU that doesn't support the required instructions.

Do you have Win 7 SP1 installed? What hardware are you running on?

Moonchild wrote: ↑

2022-11-30, 10:15

0xc000001d (the crash exception code) normally means you're trying to run Pale Moon on hardware/CPU that doesn't support the required instructions.

Do you have Win 7 SP1 installed? What hardware are you running on?

I have the same problem. I am using portable version 31.4.1. - 32 bits. The browser crashes when I try to access any website.

I downloaded the 32-bit version again on 31.41 from the official website, but it crashes even before launch.

The 64-bit version works stably.

I didn't change the hardware. OS - Win7, RAM - 2 GB DDR2, processor - Athlon 64 3000+

I'm using a Lenovo t43P with windows up to date..
I only tried it with that other module just to get you more information as to the possible cause.
I am a retired mainframe software engineer and know that the more info you can get the better.
I'll try to get that dump later when I'm free.

Attached - I hope


To Moonchild: I have been using Palemoon for years on this machine. The previous version runs just fine (as you can see by this post).
The only other thing I can think of is that I use the GB language pack normally, but this new version doesn't even get as far as allowing me to install it.

Well the only thing I can think of right now is the fact that VS2022 gave me a compiler update before 31.4.1 was released. Seems there was another update just yesterday so maybe they fixed whatever the problem was there. I can build another version of the 32-bit browser with VS 17.4.2 for you to test if that's OK?

Burn_IT wrote: ↑

2022-11-30, 14:47

I'm using a Lenovo t43P with windows up to date..
I only tried it with that other module just to get you more information as to the possible cause.
I am a retired mainframe software engineer and know that the more info you can get the better.
I'll try to get that dump later when I'm free.

Attached - I hope

Thank you. I debugged the dump file and it basically halts in a CRT routine on a mathematical floor() instruction, i.e. not in our own code, and there's nothing wrong with the instruction highlighted that throws the exception either, so it does seem to be directly related to the compiler/crt update (the runtimes were also updated)

Willingly!! Just let me know how and where to get it and I'll try it.
Any help I can give just ask! I might even be able to read a dump for you: I STRESS MIGHT. I used to debug mainframe dumps before I retired so the principle is there.

That sort of problem used to occur often in mainframe software where the library routines were updated incorrectly causing programs to fail.
I was often expected to sort out those types of dumps in the middle of the night after a heavy drinking session.
Once when I told them, when they called me, that I was too drunk to drive in, they actually sent a car to collect me..... !

Okay, I'll build a version with 17.4.2 first, and if that doesn't help i'll roll back to the previously used version of VS2022 that was used for 31.4.0.
In the meanwhile I also shot MS support a ticket to see what they say.

Give this a try:
http://testserver.palemoon.org/1742/palemoon-31.4.1.1742.win32.7z

That still crashes

I tried without my virus checker just to see if that was interfering but it still crashes.

I wonder if it is connected to the fact that this machine is not supposed to support Windows 7 though that has not affected anything at all so far and it has been for several years. (just added info)

Burn_IT wrote: ↑

2022-11-30, 18:39

That still crashes

OK, reverting to the previous known-good compiler version. I'll have another build for you shortly.

Burn_IT wrote: ↑

2022-11-30, 18:39

That still crashes

So that was a nightmare since just rolling back to the previous version wasn't possible after having upgraded once. That's why it took 3 bloody hours.
aaanyway, I managed to get the older toolset installed on the newer VS and massaging our build system to make sense of having to use the previous compiler and CRT, so fingers crossed this is an acceptable result.
http://testserver.palemoon.org/1742/palemoon-31.4.1.1433.win32.7z

That appears to work.

Is it relatively easy to include the FULL release version on the ABOUT screen since it I don't see any way of checking exactly which version is running when I have several versions lying around and there is no obvious visual difference.

Just a note;
Did you notice that the later one you sent was 1433 and the prior version was 1742.
I hope that was intentional.