What can cause this crash on exit?

[Massacre]

Faulting application name: palemoon.exe, version: 6.8.1.9615, time stamp: 0x69f22be1
Faulting module name: xul.dll, version: 6.8.1.9615, time stamp: 0x69f22c90
Exception code: 0x80000003
Fault offset: 0x015246a3
Faulting process id: 0x1568
Faulting application start time: 0x01dceeda1b09aee8
Faulting application path: C:\Pale Moon\palemoon.exe
Faulting module path: C:\Pale Moon\xul.dll

Several crashes on exit. Every crash has this specific address: 0x015246a3. Version 34.2.2 (32-bit) on Windows 10 1809 LTSC. Not 100% chance but I had this twice in a row right now.

[andyprough]

If you could post your Help - Troubleshooting info it could help, as those crashes could possibly be related to Extensions or Plugins from what I'm reading.

[Moonchild]

A code 0x80000003 means it's a deliberate breakpoint, so whatever is causing this is doing so on purpose. If it happens after about a minute, then it's the process watchdog killing Pale Moon after it had failed to shut down normally; this can happen if you've visited a site that causes the JS garbage collector to become "stuck" with a huge blob of uncleanable objects. There's no real solution for that particular problem yet. I've been experimenting with some ways around it but haven't found anything that works well, yet.

[Massacre]

So it's GC timeout actually. Explains, why it crashes when palemoon.exe persists in process list even after exiting. And its seemingly random nature comes from sites visited in specific session. I hope something could be done for this JS engine, then...

[Gemmaugr]

So it's GC timeout actually. Explains, why it crashes when palemoon.exe persists in process list even after exiting. And its seemingly random nature comes from sites visited in specific session. I hope something could be done for this JS engine, then...

Perhaps a list of the visited sites you think affect this the most would be appropriate, to affect changes (here or there)?

[Massacre]

Next crash, I will try to identify them...