Collection of random crashes

Octopuss · Post by **Octopuss** » 2026-02-03, 07:55

This is where I will post my crashes.

Faulting application name: palemoon.exe, version: 6.8.0.9517, time stamp: 0x6970a7ed
Faulting module name: mozjs.dll, version: 0.0.0.0, time stamp: 0x6970a979
Exception code: 0xc0000005
Fault offset: 0x000000000013ab0d
Faulting process id: 0x3AE8
Faulting application start time: 0x1DC945ED8A1B942
Faulting application path: C:\Program Files\Pale Moon\palemoon.exe
Faulting module path: C:\Program Files\Pale Moon\mozjs.dll
Report Id: 2fd6b63a-2e98-45c2-8c1f-ea2d976bd65e
Faulting package full name:
Faulting package-relative application ID:

Octopuss · Post by **Octopuss** » 2026-03-23, 09:50

I have to say the stability has improved dramatically over the past few months.
Didn't get a single crash for quite some time until today.

Code: Select all

Faulting application name: palemoon.exe, version: 6.8.1.9556, time stamp: 0x69a4c3d3
Faulting module name: mozjs.dll, version: 0.0.0.0, time stamp: 0x69a4c55a
Exception code: 0xc0000005
Fault offset: 0x00000000003846a8
Faulting process id: 0x3BD4
Faulting application start time: 0x1DCBA4617F22DD9
Faulting application path: C:\Program Files\Pale Moon\palemoon.exe
Faulting module path: C:\Program Files\Pale Moon\mozjs.dll
Report Id: 75ca0477-6847-4af7-baa3-4036ae8028ac
Faulting package full name: 
Faulting package-relative application ID:

Post by **Moonchild** » 2026-03-23, 10:38

https://forum.palemoon.org/viewtopic.php?f=3&t=2094

Octopuss · Post by **Octopuss** » 2026-03-23, 11:11

Which part of the post is relevant in this case?
Specs? I always run Windows 11 and latest version of PM at the time of posting.

I have numerous tabs open and keep switching, there's no way to tell what website I was on (which is why I am not starting a new thread for each crash). I would say so if it happened right as I clicked on something specific.
All of the crashes (straight to desktop) I am experiencing are completely random and not reproducible. I am only posting here because you previously said even these crash reports can sometimes help you nail some bugs down.

I can provide the troubleshooting info though.

Post by **Moonchild** » 2026-03-23, 13:18

Octopuss wrote: ↑
2026-03-23, 11:11
Which part of the post is relevant in this case?

I thought that would be clear unless you didn't read past the first paragraph.
In your case:

If you get application crashes, use AppCrashView to check the details of the app crash and post them

But yes, troubleshooting information helps.

Octopuss · Post by **Octopuss** » 2026-03-23, 19:03

I guess I got lazy writing the same environment/setup description each time but that really is stupid. I'll try to remember it next time.

Windows EventLog is the best I can provide I'm afraid. AppCrashView is not showing anything at all. I am not sure whether it's outdated or what.
edit: Oh wait, it mentions those .wer files. If that's related to Windows Error Reporting, I have that completely disabled for security reasons (and I assumed everyone else did that, just like everyone disables Cortana and similar junk).

Post by **Moonchild** » 2026-03-23, 21:48

Yeah if you hard-disabled windows error reporting you won't have .wer files (you can configure it to have them generated but not sent to Microsoft, but that's beyond the scope of this topic here).

Troubleshooting information is important to go along with a crash event report because to analyse it you need to know exactly what build of the browser you were using on what architecture and if there are unconventional configuration changes that might expose it.
When I have time I'll try to check the crash point -- in js that might not be conclusive (crash dump required in that case to get the call stack) but we'll have to see.

Octopuss · Post by **Octopuss** » 2026-03-24, 19:56

I think I managed to get it to work again (what a chore, stupid Microsoft registry and crap), so next time I might have something better to offer.

Octopuss · Post by **Octopuss** » 2026-03-25, 08:07

Well there we go.

appcrashview:

Post by **Moonchild** » 2026-03-25, 08:49

Thanks.
Well, so far you've posted 3 crashes with 3 different address offsets, meaning they were crashes in different parts of the code... Without a call stack, that will be very hard to pinpoint.

Crash1: Should have been fixed in 34.1.0
Crash2: CellIsMarkedGrayIfKnown -- should have been addressed recently but apparently still something odd going on? needs a full crashdump.
Crash3: DispatchTyped (Id.h), assuming jsid is inaccessible, also needs a full crashdump to investigate.

Octopuss · Post by **Octopuss** » 2026-03-25, 08:59

By full crashdump what exactly do you mean? Is that also related to Windows Error Reporting or where would I get those dumps from?

Octopuss · Post by **Octopuss** » 2026-03-25, 09:05

Oh wait, were you looking for this? https://drive.google.com/file/d/1xjjh6s ... sp=sharing

Post by **Moonchild** » 2026-03-25, 09:17

yes, that's what I was looking for. Unfortunately it doesn't pinpoint the problem other than that it seems to be a dangling pointer for jsid (that is potentially a priority issue). What exactly were you doing when the crash occurred? Is it reproducible?

Octopuss · Post by **Octopuss** » 2026-03-25, 09:36

No, most of these crashes seem completely random. PM window simply disappears. I believe it never happens on pages that load quickly though. It's those that grow fat, so to speak, and are subjectively slow to load, or get slower after a while. Sometimes the crashes happen after I reload a page but before it finishes reloading.
But like I said before, it's much, MUCH better now than a few months ago.

Post by **Moonchild** » 2026-03-25, 12:03

Hmm, well, the most recent one is somewhere deep in the cycle collector, so it's a tough one to address without being able to reproduce. So I'm afraid there's little to be done right this moment.

Octopuss · Post by **Octopuss** » 2026-03-25, 13:55

I believe I can make Windows save full dump. Would that help? I think what I shared is a small one or something. I don't really understand these things.

Post by **Moonchild** » 2026-03-25, 17:02

No, for this one I really do think I need a way to reproduce it locally... and run a debug build through it.

Octopuss · Post by **Octopuss** » 2026-03-26, 10:23

I've just had another crash. It was on an extremely simple website that runs barely any scripts at all (I assume, it's olschool-like text only discussion board). I tried editing an ad I had there, PM suddenly stopped responding when I clicked into an edit field, and crashed after about 3 seconds. Not reproducible of course.

I was messing around OS settings and only have 2GB crashdump this time (I'll change it back to small one). Do you want me to upload it anyway?

Code: Select all

Faulting application name: palemoon.exe, version: 6.8.1.9556, time stamp: 0x69a4c3d3
Faulting module name: mozjs.dll, version: 0.0.0.0, time stamp: 0x69a4c55a
Exception code: 0xc0000005
Fault offset: 0x00000000003846a8
Faulting process id: 0x2C3C
Faulting application start time: 0x1DCBC4D7FCF633F
Faulting application path: C:\Program Files\Pale Moon\palemoon.exe
Faulting module path: C:\Program Files\Pale Moon\mozjs.dll
Report Id: f2a2f684-de98-44bc-a442-f7d5845b76d3
Faulting package full name: 
Faulting package-relative application ID:

appcrashview

Post by **Moonchild** » 2026-03-26, 10:34

That one is the same offset as Crash #2, so yes that would help. Please 7-zip pack it.
You can use the FTP server to upload it privately, see https://forum.palemoon.org/viewtopic.php?f=19&t=13044 for info in that.

Octopuss · Post by **Octopuss** » 2026-03-26, 10:50

It seems like I can't connect to the FPT despite having port 21 forwarded

Total Commander will hang on "Download" message. I have no idea what to do about it since I am not a networking person and I haven't used FTP in like 15 years.

Anyway, the dump is here: https://drive.google.com/file/d/1-d9sg5 ... drive_link

Pale Moon forum

Collection of random crashes

Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes

Re: Collection of random crashes