Pale Moon 32.4.1 APPCRASH

[Kris_88]

PM 32.4.1 win64 portable, windows 10.
One tab with a video on YouTube was open. The crash happened when I was working in another application and the processor was heavily loaded. I didn't see any crashes in the previous version of Pale Moon.

Faulting application name: Palemoon.exe, version: 6.3.0.8671, time stamp: 0x65155af7
Faulting module name: xul.dll, version: 6.3.0.8671, time stamp: 0x65155da9
Exception code: 0xc0000005
Fault offset: 0x0000000000657824

[Piotr Kostrzewski]

I'm not saying that's why, but when I had this exception code in another application, it turned out that my RAM was damaged.

[Kris_88]

, it turned out that my RAM was damaged.

In my case this is unlikely. The memory was not occupied more than usual and I did not observe any memory problems at all.

[Piotr Kostrzewski]

In my case this is unlikely. The memory was not occupied more than usual and I did not observe any memory problems at all.

That's why I emphasize that this could be the reason, but it doesn't have to be.
I haven't noticed any problems before either.

[Kris_88]

That's why I emphasize that this could be the reason, but it doesn't have to be.

Of course, this is possible. But then my other applications would crash too. So far this has not happened.

search.php?keywords=0xc0000005

[Piotr Kostrzewski]

Of course, this is possible. But then my other applications would crash too. So far this has not happened.

search.php?keywords=0xc0000005

Also, only one application crashes for me.
The others don't.
Only this one achieved significant memory consumption.

[Kris_88]

Also, only one application crashes for me.
The others don't.

Then most likely everything is fine with your RAM.

[Piotr Kostrzewski]

Then most likely everything is fine with your RAM.

I wish it were so.

If so, that's great, but I won't use that app for now.

[Moonchild]

The crash address doesn't make much sense, it's in a symbol jump table dealing with image layers, but not actually in executed code.
If it persists, can you try to catch a dump file?

[Kris_88]

Okay, I'll try to catch this in more detail if it happens again.

[markd89]

I'm seeing segmentation fault sometimes in Linux which is new in the new version.

[Harkonnen]

Palemoon has been occasionally segfaulting since a last few version, but with 32.4 it has upgraded from a crash once in a few days or even weeks to crash every few hours of active usage

[Moonchild]

That must be annoying - without details about the crash we can't do anything about it, though. My browser has been rock-solid stable with the latest version, even leaving it on for days on end. And yes, I use the release version as my daily driver, so exactly the same thing everyone else uses.

[Harkonnen]

What info can be provided? For me, crashes (linux, segmentation fault) started with 32.2.0, and never fully gone away since then. I had updated from Debian 10 to Debian 12 in meantime, but that didnt affect this. Before 32.4.0 they werent happening very often, maybe once in 2-3 days.

P.S. I have just realized that i am using 32.4.01, not 32.4.1, because Steve's repository have not updated to 32.4.1. Will try tarball version now and report back.

[Night Wing]

P.S. I have just realized that i am using 32.4.01, not 32.4.1, because Steve's repository have not updated to 32.4.1. Will try tarball version now and report back.

I have been using the tarball version of Pale Moon since it's inception and that was way back in January of 2014. The only times Pale Moon has crashed on me when I visited a "very poorly coded website" where the maintainer of the website was poor at writing code for the website. And those site crashes are very very far and very very few inbetween.

And at this time, I am using the 64 bit GTK2 build of linux Pale Moon 32.4.1 running in both 64 bit linux Mint 21.2 (Victoria) Xfce and 64 bit MX Linux 23 (Libretto) Xfce.

As a side note. I prefer the linux GTK2 builds of Pale Moon over the GTK3 builds. Just my personal preference.

[Kris_88]

It seems that in my case there was a lack of some system resources (possibly GDI objects).
That is, the Pale Moon is not the cause. The only possible complaint about Pale Moon is the lack of some checks.

[Moonchild]

The only possible complaint about Pale Moon is the lack of some checks.

There is unfortunately no real way for Pale Moon to check this, as things like GDI object caps and subsequent allocation failures are abstracted by the O.S.
To be fair, it's been a very, very long time since I heard of anyone running into this cap (I think the last time I ran into it was on Win 9x... ). If you're on that low-end of hardware, you really should consider getting an upgrade of some sort. You should be able to get something halfway decent for very little money on the various online marketplaces for second hand goods.

[Kris_88]

If you're on that low-end of hardware, you really should consider getting an upgrade of some sort. You should be able to get something halfway decent for very little money on the various online marketplaces for second hand goods.

I seem to have a normal computer. And in any case, I don't think it's related to the equipment. In short, I don’t know for sure what happened there.
So far the problem hasn't happened again...

[Moonchild]

Chalk it up to gremlins!

[Harkonnen]

P.S. I have just realized that i am using 32.4.01, not 32.4.1, because Steve's repository have not updated to 32.4.1. Will try tarball version now and report back.

Crashed twice in 1.5 days of using 32.4.1 tarball