We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.

The crash report is several pages of data. We need the report numbers to see the whole report.

1. Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted (and Unsubmitted, if any) Crash Reports will appear, similar to the one shown below.
2. Copy the 5 most recent Submitted Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.

Note: If a recent Report ID does not start with bp- click on it to submit the report.

(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

Thanks, Paul. I'll do this the next time it crashes; shouldn't be more than 24 hours. Of course now that I'm waiting for it to crash, it'll probably keep me waiting.

Treloar's Law of Inverse, Perverse Causality In any dichotomous situation, the more you prepare for one the greater the likelihood of the other.

Hi Bill

All working okay now?

I haven't really done anything, because so far Firefox hasn't hung up again. It doesn't happen every day, but when it does, it's quite persistent. I'd like to give it through the end of the week before I conclude it's really not happening anymore..

FWIW, there was a Firefox update in the last couple of days, so maybe some tweak fixed it?

There was only one crash report that started with BP-: here is bp-0adf7d05-336a-49bd-bb64-a3d420251013

Hope that helps.

Oops! MY bad. Here are other BP reports:

bp-0adf7d05-336a-49bd-bb64-a3d420251013 10/13/2025, 12:22 PM bp-9052d4b3-dec1-4e6d-a7e7-7c9c30251013 10/13/2025, 12:27 PM bp-bf2a2ce6-ccba-4f1c-a66d-662800251013 10/13/2025, 12:27 PM bp-a6f1f182-9d19-440a-86f1-698320251013 10/13/2025, 12:27 PM bp-11b1a406-d578-477a-be56-aff890251013 10/13/2025, 12:27 PM

Sorry for re-entering this issue — I couldn't find this submission until after I asked the question again.

Clearly, the problem still persists, as it's happened again today. I went to about:crashes and see crash reports from 10/13 (most previously reported above) but none from today, although it crashed at least 4 times before I rebooted this morning.

Any advice?

Hi Bill,

That sounds really frustrating! You might want to try creating a Firefox Crash Report — you can do this by going to about:crashes in your browser, which will show recent crash IDs. You can then submit these to Mozilla so their team can investigate.

Also, sometimes issues like this are caused by hardware acceleration or lingering profile corruption. You could try starting Firefox in Safe Mode (Help → Troubleshoot Mode) to see if it stabilizes. Tracking your steps and crashes using Phonexa or a similar tool can also help pinpoint patterns in what’s triggering the crashes.

Hope this helps and that you get Firefox running smoothly again!

Three of the reports are for "shutdown hang." These are created when a watchdog process recognizes that Firefox's post-exit cleanup is taking too long. They don't point to the specific reason for the delay, but often it is that Firefox is set to delete cookies or other history when it closes, and for some reason, that is taking much longer than usual.

The first report on your list was a crash in an Intel graphics driver.. I can't tell what Firefox was trying to do when that happened. The last report on your list was from the time of Firefox 140.0.4, so that probably isn't related to your recent crashes.

Since Firefox is freezing, it probably isn't capturing any information about what is going wrong. If you keep Firefox's built-in Task Manager (Shift+Esc) open in a tab, are you able to view that list when the problem occurs and see whether any of the processes seem to be consuming way too much CPU?

wirkutskijkarl - Thanks for your response. How do I submit crash reports to Mozilla? Not through this forum?

jscher2000 — Thanks for your suggestions. I don't think I have Firefox set to clean up when it closes. I do manually clear all data every two weeks. Could that be what's going wrong? I haven't tied the clearing and crashes together, time-wise.

I'll try to remember to keep the Process Manager open until the next time the problem occurs. I have run the Windows Task Manager to check CPU usage and haven't seen Firefox or anything else maxing it out; I'll try to check it the next time the crashes happen again..

Apparently these are considered "hangs", not "crashes". I'm trying to figure out the difference.

The following article has general suggestions for resolving freezes. Replacing the Places database will remove all your history, so before that, I would suggest running the maintenance routine mentioned I'll describe below the link.

Firefox hangs or is not responding - How to fix

Places Maintenance

Try the "Verify Integrity" diagnosis and repair function. That's here:

Open Firefox's Troubleshooting Information page using any of these methods:

• "3-bar" menu button > Help > More Troubleshooting Information
• (menu bar) Help > More Troubleshooting Information
• type or paste about:support in the address bar and press Enter

Near the bottom, there is a section titled Places Database -- that's the file which stores history and bookmarks. Click the button labeled Verify Integrity. There may be a 10-15 second delay before results appear.

If all is well, the report that appears below the button should start with:

> Task: checkIntegrity
+ The places.sqlite database is sane
+ The favicons.sqlite database is sane
> Task: invalidateCaches
+ The caches have been invalidated
> Task: checkCoherence
+ The database is coherent

Hopefully yours reports that the databases are sane and coherent. The other lines report on whether it could be vacuumed (this is similar to packing an MS Access database) and lists various stats.

Not sure if this is related, but someone sent me a link to a post on Instagram, and for the past 4-5 minutes the page has been loading with the Firefox Process Manager showing it taking 100% CPU plus about 5-20% CPU taken by Firefox itself on top of that.

Loading the same Instagram page in Chrome generated a "page unresponsive" warning, so the issue is likely with Instagram, but when I check Task Manager while Chrome is trying to load the page, I see I'm only using no more than 23% CPU. Does that provide a clue as to what may be going on?

The crashes recurred today. I ran about:support and opened up recent crashes, but all of them are from more than two weeks ago. I copied Troubleshooting Info in case it's needed. Then I looked at the Firefox Task Manager and find something consuming 75-80% of CPU:

Utility (24548) Windows Media Foundation Media Engine CDM

Can that be the culprit?

I would expect to see "Windows Media Foundation Media Engine CDM" when playing MP4 videos (and probably some other formats). Maybe a tab restored after the crash is processing a lot of video??

Is "hardware acceleration" disabled in your Firefox? There is a way to do that manually, but usually it's not necessary or beneficial. It also could happen automatically if Mozilla detects that your graphics driver software is incompatible. Maybe check:

• Upgrade your graphics drivers to use hardware acceleration and WebGL
• Firefox's performance settings

Thanks, jscher2000 — no videos of any sort are playing. The only tabs open were this one, my Pipeline CRM, Google Calendar, and a Thunderbird Forum tab.

I'm updating all out of date drivers now via CCleaner. But none seem to be related to web browsers or hardware other than the integrated camera in my laptop.

Firefox is set to "use hardware acceleration when available".

These hangs may occur only once a week, so it may be as long as a week or so before I'd expect the issue to resurface.

jscher2000: I ran the about:support and clicked the Verify Integrity button. What you told me to expect to see all matches EXCEPT:

These two lines are missing: > Task: invalidateCaches + The caches have been invalidated

Does that provide any evidence of what's going wrong?

Thanks! Bill

Hi Bill, it seems to have changed from when I saved that example. Here's what I see right now:

> Task: checkIntegrity
+ The places.sqlite database is sane
+ The favicons.sqlite database is sane
> Task: checkCoherence
+ The database is coherent
> Task: expire
+ Database cleaned up
> Task: vacuum 

et cetera

But more importantly, is it working now?

That looks like what I see. Unfortunately, no it's not fixed, happening most recently 2 days ago.

A restart of Firefox doesn't fix it, but a reboot of the whole PC does. I wonder if it's a conflict with something else.?