Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
Open

Firefox Crashes Hourly

Colin WG

And it is rather annoying that the report does not tell me which addon is misbehaving either. I do know it runs just fine without any addons enabled so hence, the problem lies with a buggy addon and I'm left in the dark about which one.

And it is rather annoying that the report does not tell me which addon is misbehaving either. I do know it runs just fine without any addons enabled so hence, the problem lies with a buggy addon and I'm left in the dark about which one.

All Replies (6)

Yeah, that’s frustrating. Since you’ve confirmed Firefox is stable with add ons disabled, I’d enable them again and disable half of them at a time, then restart Firefox and see if the crashes continue. Once you narrow it down to a few, enable them one by one until you find the culprit.

The crash report usually won’t tell you which add on caused it directly, so this is probably the quickest way to isolate it.

Anything interesting in the crash logs worth sharing?

  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.)

Fx115aboutcrashes

jbr said

Anything interesting in the crash logs worth sharing?

bp-32518c96-5ed9-4982-8e64-f90cb0261002 10/2/2026, 12:54 PM bp-75cb9bfa-a3fb-43be-9a34-275ba0261001 10/1/2026, 4:01 PM bp-5c640a32-c621-42bf-9739-793600260917 9/17/2026, 9:32 AM bp-826f5550-b72d-4483-9c51-670420260907 9/7/2026, 10:47 AM bp-1b5f8794-6a2e-4e66-8b2f-ec25e0260817 8/17/2026, 4:02 PM

I've looked at the actual reports but I have no references to what each part means.

However, we might be able to narrow it down to one of the extensions I removed, but I made the mistake of not noting the actual proper names of the extensions.

These were disabled: Overlay Disabler / Remover - cannot remember the exact name Useragent Switcher Greasemonkey Adblock for Youtube

I generally see out–of–memory errors (and something from Comodo security also getting in the way) — but not an exact spot where it crashes constantly — so my guess is a runaway userscript in greasemonkey that causes some infinite looping or recursion and then exhausts system resources.

That said, you're at 90% RAM and just a couple hundred MB virtualmem so you're basically at the system limit you have available.

(What I don't see however, is hourly crashes. There's few OOM small like the above, few SVG render limits weeks ago on previous version, and some shutdown hangs on dirty metadata cleanup few versions back — so it's possible if you're witnessing crashes hourly, these are not logged.)

jbr said

(What I don't see however, is hourly crashes. There's few OOM small like the above, few SVG render limits weeks ago on previous version, and some shutdown hangs on dirty metadata cleanup few versions back — so it's possible if you're witnessing crashes hourly, these are not logged.)

The system did not always seem to catch the crash, some times the window just vanishes and I'm left with nothing.

Restart firefox and do get the "resume session" page however.

Still et spørsmål

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.