Sorry to hear about this problem.

Two reports have the crash signature "pages_decommit" (with 99% of the reports on Linux and 1% on Windows?). This seems to be an error that occurs during memory allocation/deallocation.

One report has the crash signature "@0x1ef9153b627" which I don't know how to interpret.

Two reports have the crash signature "js::gc::Cell::storeBuffer". I don't know about heaps and buffers, but this might also be memory related. In the Crashing Thread section, they have some red rows with values like "@0x0000025a811a614f" -- are those memory addresses??

Unfortunately, I don't see a lot of clues here as to what is going wrong.

Can you associate it with particular sites/pages/content/features?

Do you use any security software with "anti-exploit" features?

Thanks for the response, the crashes happen a lot on facebook, youtube, reddit, and on random sites as well.

for "anti-exploits", I am running a pi-hole on a separate linux machine set as my DNS to block tracking and ads.

If that is the cause, do you have any idea how I should set my firefox DNS settings to prevent these crashes?

Hi, I don't think your DNS is an issue.

The way anti-exploit software works is to inject into or wrap around Firefox processes to protect memory that isn't allocated to Firefox.

The sites you mentioned have a mixture of media (text, images, video), so hardware acceleration of graphics is a possible point of failure. That is disabled in Troubleshoot Mode, but you also can turn it off in regular mode using a setting. See: Firefox's performance settings.

Does it still happen with default settings in a new browser profile? An easy way to test a new profile is to install Developer Edition and see if it happens there or refresh your existing profile. Make sure you stay signed out of your sync account when testing.

Thanks for the replies guys, unfortunately the crashes still happen after I refreshed the profile and during troubleshooting mode.

Here's the crash report after I refreshed the profile: bp-b5e3f83d-92cd-4e74-900d-e36370240428 after that I went to troubleshooting mode and crashed again after 5mins: bp-707c995d-9e33-416f-b8cd-8a32a0240428

Both crashes happened while I was listening/watching in youtube. Could this be a hardware issue?