Firefox Community Forum

Firefox frequently and continuously force-closes the entire program on me, multiple times a day. I have tried updating my computer, checking for Firefox updates, and any extension updates that could be affecting this. HOW DO YOU MAKE THIS STOP?

Every time I run Firefox 152.0b10 on Macos Tahoe 26.5.1 Mini it flickers and crashes. Its reporting a webrender compositor error. I made a new installation and it worked but I will have lost all my extensive userChrome/Content customization, as well as hours of time today and more hours to come transferring across and doing things like typing this out and checking versions.

And it flickers awfully on the new installation so is unusable. What should I do? I'm typing this on my Macbook Pro with M3 Pro & Macos Sequoia 15.2, which is not running Tahoe as it bricks all the Adobe software on the laptop. I refuse to rent Photoshop and Premiere for the exhorbitant price Adobe charge, and am transitioning to DaVinci products but not yet done learning.

I have cleared all caches, reset all the hardware acceleration stuff to off or force-disabled, and done everything else suggested by any and every AI agent, like switch off Widevine for a bit then on, or stop UBlock0 running in any way, shape or form. Things change when such things are done but don't work.

You updated your browser on my pc today. Now I can’t open it. It opens but has not opened any sites. I’ve had to use bing. I’ve used your browser for several years but unfortunately I’ve not been able to. It locks up when I try to open YouTube. The blue circle starts and locks up. Too bad.

For the past few weeks I have been having constant crashes in the form of tabs crashing and complete browser crashes. I have tried disabling every single extension, still crash. it even crashes in troubleshoot mode. In fact its crashed while I am writing this. Seriously thinking about giving up entirely on this browser and switching.

the latest crash report submitted : bp-5ca96001-20a8-4097-ae0d-9a42d0260630 bp-aba4b1dc-6248-4516-bf35-3f19d0260630 bp-c222bd57-f884-49e6-a3a7-be7130260630

610c857a-a2cb-4418-acab-c5427191921a 6/18/2026, 1:48 PM a8a404a8-d04f-4ab9-a983-bee673c80a81 6/18/2026, 1:45 PM 9369f2bf-e222-40c9-8891-459f2fc4c135 6/18/2026, 1:15 PM 45e527f4-d682-44cc-87bb-7e53c62166cd 6/18/2026, 1:01 PM 43ed298b-1639-45e3-b57d-af22242193f5 6/18/2026, 12:57 PM e283cc13-e637-484f-b540-7b38bf9451fd 6/18/2026, 12:46 PM 77f667a2-e11d-4ca5-99fb-b45d03a58d39 6/18/2026, 12:43 PM

I'm reading https://support.mozilla.org/en-US/kb/mozillacrashreporter#w_when-firefox-crashes

Firefox crashes but I have never seen the crash reporter on my 6.18.10-200.fc43.x86_64 Fedora 43 system with budgie-desktop 10.9.3

Is the crash reporter discontinued?

I usually use firefox to download things, and watch videos, however, sometimes, when I change tabs, try to minimise firefox, close a pop up, even if I just pause a video, it randomly decides to instead completely freeze and require the app to be completely restarted, and it occasionally decides to roll back my search history.

In fact, Firefox crashed as I was writing this, i'm lucky my progress was saved, these issues have made firefox completely unusable about 70%-80% of the time, and i'm running out of browsers to switch to, opera is run on lies, chrome is just bad, and now firefox is dying.

Just for reference, no other application or web browser that has ever been on my current device has ever acted like this, I'm currently using a decent PC running Windows 10

While playing Free Games.org and Free Mahjong also on AOL Mail Firefox crashes after a few moments. I performed security scans and restarted, still crashing.

Following my traumatic brain injury I do have a reading disability search that perusing your articles could take me up to a week.

As you see I am running Windows 10 on a laptop which Microsoft said I was good for another year using this OS. Your latest download executed and after 2 reboots continuously crashes after trying to view any of the five windows a browser I had open with multiple tabs in each.

Every time I attempt to log into X.com the Firefox browser stops working entirely. Dead. Nothing. Won't open or function. Need to restart my computer to access and use Firefox. This does not happen when I use Chrome.

Since the latest Firefox latest update yesterday (02/24/2026), each time I try to open a new tab in Firefox it crashes. I get a "gah, your tab has crashed" message but when I hit the "restore" link nothing happens. How do I fix this at my end? Thank you.

I don't want to spend any more on my PC. It was the largest amount of money I had ever seen when I first bought it. Even if I have way more resources now, I don't believe that a few faulty locations in my memory should be causing so many problems for myself and for developers who have no clue why their users keep crashing.

It is either my RAM or VRAM. Disabling XMP on my RAM dampened these issues but couldn't fully solve them.

It's exactly as I said. Normal programs just crash. Kernel-level programs or anti-cheats can entirely blue screen my PC. It all has to do with where these programs are writing to in my hardware. It's only a few locations that I have faulty. Most programs work fine. Most games work fine. Most crashes are very transient.

Firefox is a transient and common crasher for me. It's so painful to be scrolling a page and have the page crash, just for the previous page to load instead of the newer one that I was on, and on top of that I could also be losing work or effort.

I know this isn't exactly a dev support page, but this problem is so recurring that I don't know what to think anymore. There has to be a way to check which memory locations are fried without causing a bluescreen or crashing the program. Maybe it's a Windows issue and devs could easily fix it, if it weren't for Windows bottlenecks like labelling the faulty locations as "protected". I've seen at least 1 crash where the output said something like "Error: tried writing to protected location" blah blah blah then it spit out some hexcode or exact location and blahblahblah. And that was the entire error message.