![Firefox Keeps Crashing? 16 Fixes That Actually Work [2026]](/images/blog/firefox-keeps-crashing-fix-hero.webp)
The tab freezes mid-scroll, the window goes gray, and a second later Firefox is gone entirely — or it reopens with a "Restore Previous Session" prompt as if nothing happened. Firefox crashing is a recurring complaint we handle at IT Cares, and while it affects a smaller share of users than Chrome or Edge simply because fewer people run it as their default browser, the underlying causes are just as fixable — usually within twenty minutes and without losing a single bookmark, saved password, or open tab. It also doesn't require any paid software; every fix below uses tools already built into Firefox and your operating system, and none of them require reinstalling your entire operating system as a starting point.
This guide walks through all 16 fixes in the order we actually use during remote support calls, starting with Firefox's own built-in Troubleshoot Mode — a genuinely underused feature that disables extensions and hardware acceleration simultaneously, telling you within two minutes whether an add-on, your graphics driver, or something deeper in your Firefox profile is behind the crash. We'll also cover the Refresh Firefox feature, how to read Firefox's local crash log at about:crashes, and what to do if crashes are tied to one specific website rather than the whole browser.
Firefox crashes tend to fall into the same three broad patterns as any browser: crashes tied to a specific site or tab, crashes that happen unpredictably during normal use, and crashes that happen immediately on launch before the window even appears. We've flagged which fixes address each pattern throughout this guide so you can skip straight to what's most likely to help.
It's also worth understanding why Firefox's crash causes look slightly different from Chrome or Edge under the hood. Firefox runs on Gecko, Mozilla's own rendering engine, not the Chromium engine that powers Chrome, Edge, Brave, and most other modern browsers. That means extension APIs, hardware acceleration handling, and even how the browser recovers from a bad page are all implemented independently by Mozilla rather than shared with the Chromium ecosystem. This is generally a strength for privacy and browser diversity — but it also means Firefox-specific crash quirks exist that you won't find identical troubleshooting advice for in a generic "browser crashing" guide written primarily around Chromium behavior.
None of this means Firefox is inherently less stable — plenty of long-time users run it for years without a single crash — but it does mean that generic advice like "just clear your cache" often misses Firefox-specific tools that solve the problem faster, particularly Troubleshoot Mode and Refresh Firefox, neither of which has a direct equivalent that works quite the same way in Chromium-based browsers.
Is it a full crash, or is Firefox just "Not Responding"?
If Firefox's window goes gray or unresponsive but doesn't fully close, and closing/reopening restores it instantly with your tabs intact and no crash report window, you likely have a temporary freeze rather than a true crash — usually caused by a slow-loading script on a specific page or a hung extension. Fix 2 (Troubleshoot Mode) and Fix 6 (hardware acceleration) are the most likely fixes for this pattern specifically.
Normal Firefox Behavior vs. a Real Crash Problem
| Situation | Normal / Expected | Crash Problem |
|---|---|---|
| Tab crash ("Gah. Your tab just crashed.") | Rare, on one heavy site | Multiple sites, several times a day |
| Whole window closes | Never during normal browsing | Happens with 2-3 tabs open |
| Launch behavior | Window appears in 1-2 seconds | Crashes before window renders, or right after |
| Restore Previous Session prompt | Only after a manual restart or update | Appears on nearly every launch |
To check what Firefox is doing in real time, type about:performance into the address bar — this shows every open tab, extension, and subframe with its current energy and memory impact, similar to a built-in task manager. Watch this tab in a pinned position while you browse normally; the moment something crashes or freezes, glance at whichever process was spiking right before, and you'll usually have a strong lead on the cause.
Is This Actually a Firefox Problem, or a Windows/Mac Problem?
Before working through the fixes below, take a moment to check scope. Open two or three other applications you use regularly and use them normally for 10-15 minutes. If they crash or freeze too, the problem is very likely at the operating system or hardware level — a failing graphics driver affecting every application, insufficient RAM, or a corrupted system file — not something specific to Firefox. In that case, jump to Fix 6 (graphics driver), Fix 11 (system diagnostics), and Fix 16 (hardware check) rather than spending time on Firefox-specific fixes like extensions or profile refresh, which won't fix a system-wide fault.
If Firefox is the only application misbehaving while everything else runs perfectly, the cause is almost certainly contained to the browser — its extensions, its profile data, its cache, or a Gecko-specific interaction with a website or your antivirus. That's the more common scenario, and it's genuinely good news: browser-scoped fixes carry no risk to your other applications, files, or system stability.
There's a middle category worth calling out too: applications that share components with Firefox specifically, rather than the system as a whole. If other Mozilla products (Thunderbird for email, for instance) are also unstable, or if other applications that embed a Gecko-based rendering component are misbehaving, that narrows the search toward something in your shared Mozilla profile folder or a system library both programs depend on, rather than either a pure browser issue or a pure hardware issue. This is a less common pattern than the other two, but worth ruling out if you use multiple Mozilla products day to day.
Can't fix it yourself? Skip the trial-and-error.
Our certified bilingual tech remotes in, reads your system logs, and resolves it on the spot — same day, from $119.99. No fix, no fee.
16 Fixes for Firefox Crashing
Check about:crashes First
Type about:crashes into the address bar to see a local log of every recent Firefox crash with a timestamp. This takes 20 seconds and gives you the single most useful diagnostic clue available: the pattern across entries. Crashes clustered right after Firefox starts point to a startup or extension conflict. Crashes spread evenly through the day point to a specific site or extension trigger. Timestamps that line up with a Firefox update, extension install, or graphics driver update tell you exactly what to investigate first, rather than guessing.
Launch Troubleshoot Mode (The 2-Minute Diagnostic)
Click the menu button (three horizontal lines, top right) > Help > Troubleshoot Mode…, then click Restart in the confirmation dialog. This relaunches Firefox with all extensions and themes disabled and hardware acceleration turned off — the two most common crash triggers — without permanently uninstalling anything. Browse normally for a few minutes, especially returning to whatever site or task triggered the crash before. If Firefox is stable in Troubleshoot Mode, exit it (there's a button in the same menu) and move to Fix 3 to narrow down exactly which extension or setting was responsible.
Disable Extensions One at a Time
If Troubleshoot Mode fixed it, go to about:addons, click Extensions in the left sidebar, and disable them all. Re-enable one at a time, relaunching Firefox normally between each and testing for a few minutes, until the crash returns — that's your culprit. Ad blockers, VPN extensions, old password managers, and download managers are the most common offenders. Once identified, check the extension's page on addons.mozilla.org for known compatibility issues, update it to the latest version, or remove it entirely if it's abandoned by its developer.
Update Firefox to the Latest Version
Click the menu button > Help > About Firefox. This opens a dialog that automatically checks for and downloads updates — click Restart to update Firefox if one is available. Mozilla ships a new stable release roughly every 4 weeks, and crash-related regressions are typically patched within 1-2 weeks of being widely reported. If your crashing started suddenly and recently, there's a real chance a fix has already shipped and you simply haven't restarted to receive it.
Clear the Cache and Cookies
Click the menu button > Settings > Privacy & Security, scroll to Cookies and Site Data, and click Clear Data (check both boxes). Alternatively press Ctrl+Shift+Delete for the quick dialog, set the time range to "Everything," and clear cache plus cookies. A corrupted cache file is a common cause of crashes tied to specific websites — Firefox tries to load a damaged cached resource and the content process dies. This is especially worth trying if crashes concentrate on 1-2 sites you visit often rather than happening everywhere.
Turn Off Hardware Acceleration
Click the menu button > Settings > scroll to Performance > uncheck "Use recommended performance settings" > uncheck "Use hardware acceleration when available" > restart Firefox. Hardware acceleration offloads rendering and video decoding to your GPU for smoother performance, but it's also one of the most common sources of crash-on-launch and random freeze issues — particularly on laptops with older integrated graphics, dual-GPU (switchable graphics) setups, or outdated drivers. This single toggle resolves a significant share of the Firefox crash cases we see.
Update Your Graphics Driver
Press Windows key + X > Device Manager > expand Display adapters > right-click your GPU > Update driver > Search automatically. For more reliable results, download directly from the manufacturer: Intel (intel.com/content/www/us/en/download-center), Nvidia (nvidia.com/drivers), or AMD (amd.com/support). On a Mac, graphics drivers update through standard macOS updates (Apple menu > System Settings > General > Software Update). An outdated or corrupted graphics driver is the leading cause of GPU-related Firefox crashes, since Gecko's compositor communicates directly with it for every rendered frame.
Check for Antivirus and Security Software Conflicts
If you run a third-party security suite (Avast, AVG, Norton, McAfee) and crashes started after a security software update, this is a plausible cause — several of these products hook into browser processes to scan web traffic, and version mismatches between the security suite and a new Firefox build have historically caused instability. Update your antivirus to the latest version first. If crashes continue, temporarily disable real-time/web protection for 10 minutes as a test (re-enable immediately after). If Firefox stabilizes during that window, contact your antivirus vendor for a compatibility fix or consider using Microsoft Defender (Windows) or macOS's built-in protections instead. Corporate firewall and web-filtering software (common on managed business laptops) can produce a similar pattern if it inspects encrypted HTTPS traffic, so if you're on a work device and this test resolves the crash, loop in your IT department rather than permanently disabling the protection yourself.
Create a New Firefox Profile
Type about:profiles into the address bar, click Create a New Profile, follow the wizard, then launch the new profile and sign in to Firefox Sync to restore bookmarks and passwords (give it 1-2 minutes to sync down). This leaves behind any corruption in the old profile's preferences, cache, or extension storage while restoring your saved data via account sync. If Firefox stops crashing on the new profile, the old local profile was corrupted — you can delete it afterward from the same about:profiles page once you've confirmed everything synced correctly.
Refresh Firefox
Type about:support into the address bar, click Refresh Firefox… in the top right, and confirm. This resets Firefox to its default state — removing extensions, themes, and custom settings — while preserving bookmarks, passwords, browsing history, and cookies. Firefox automatically creates a backup folder of your old profile on the desktop first, so nothing is permanently lost. This is the single most effective fix for crashes caused by accumulated settings corruption that a simple profile switch doesn't fully address, and it takes under a minute.
Run a System File Check (Windows) or Disk Utility (Mac)
On Windows, open Command Prompt as Administrator and run sfc /scannow to check for and repair corrupted system files that Firefox depends on for rendering, networking, and security. On Mac, open Disk Utility (Applications > Utilities), select your startup disk, and click First Aid to check for and repair disk-level issues. Firefox crashes are sometimes tied to underlying OS-level corruption rather than anything in the browser itself, and this step rules that out directly.
Check RAM Usage and Tab Count
Type about:memory into the address bar and click Measure for a detailed breakdown of what's consuming RAM inside Firefox. On systems with 8GB RAM or less, having 30-40+ tabs open can push the system into swapping, showing up as freezing or forced crashes. Firefox's multi-process architecture shares content processes across tabs more efficiently than some browsers, but extreme tab counts still matter. Consider an extension like OneTab to consolidate inactive tabs into a single list, or simply bookmark and close tabs you're not actively using.
Scan for Malware
Open Windows Security > Virus & threat protection > Scan options > Microsoft Defender Offline scan (Windows), or on Mac use a reputable scanner like Malwarebytes for Mac. Browser hijackers and adware are a known cause of erratic crashes across all browsers, particularly if you've noticed unexpected new tabs, a changed homepage, or search redirects alongside the crashing. A full offline scan takes 15-20 minutes and rules out malware entirely as the cause.
Switch to the Extended Support Release (ESR)
If crashes started specifically after a Firefox update and persist despite the fixes above, download the Firefox ESR (Extended Support Release) from mozilla.org/firefox/enterprise. ESR receives the same security patches as regular Firefox but on a slower release cycle focused on stability over new features, which can avoid a specific regression in the current mainline release. This is a reasonable temporary step while waiting for Mozilla to patch a known issue in the standard release channel.
Uninstall and Reinstall Firefox
As a near-last resort: uninstall Firefox through Settings > Apps > Installed apps (Windows) or by dragging it to Trash (Mac), restart your computer, then download a fresh copy from mozilla.org/firefox. This clears every trace of local installation-level corruption. Sign back in to Firefox Sync afterward to restore bookmarks, passwords, and extensions. Budget about 15 minutes including the restart and re-sync. Note that your profile data lives separately from the installed application, so this step is safe even without first backing anything up — though Refresh Firefox (Fix 10) resolves the same class of problem faster in most cases.
Check for a Hardware Problem (RAM or Storage)
If other applications besides Firefox are also crashing randomly, the root cause likely isn't Firefox at all. On Windows, run Windows Memory Diagnostic (search it in the Start menu, select "Restart now and check for problems") to test for faulty RAM. On Mac, hold D at startup to run Apple Diagnostics. Failing memory modules or a failing drive produce exactly the kind of random, hard-to-reproduce crashes that get misattributed to "Firefox being buggy" when the actual cause is hardware affecting every application on the machine.
Managed/work computers: check for enterprise policies
If your Firefox is managed by a workplace IT department, administrative policies deployed via a policies.json file or enterprise MDM can restrict settings changes and occasionally cause instability, particularly with forced extension installs. Type about:policies to see which settings are locked by an administrator — if several show as actively enforced, the safest first moves are Fix 1 (checking about:crashes) and Fix 4 (updating Firefox), since neither touches policy-managed settings. Beyond that, route further troubleshooting through your IT department to avoid disrupting a deployed security configuration.
Understanding the Mozilla Crash Reporter
When Firefox crashes, you'll often see the Mozilla Crash Reporter window appear right after — a dialog asking whether you'd like to send a report to Mozilla. Many users click it away out of habit without realizing what it does or whether it's worth the ten seconds it takes. It's genuinely worth sending: the report includes technical details about what the browser was doing in the moments before the crash (which extensions were active, memory state, the specific code path that failed) but does not include your browsing history, saved passwords, or personal file contents by default.
Every crash report contributes to what Mozilla calls a "crash signature" — a fingerprint of the specific failure pattern. When a signature receives enough reports in a short window, it gets automatically flagged and prioritized in Mozilla's internal bug tracker, which is a meaningful part of how widespread Firefox crash bugs get identified and fixed quickly in upcoming releases. You can review your own submitted (and unsubmitted) crash reports any time at about:crashes, and clicking into any individual report shows you the crash signature ID, which you can search directly on Mozilla's Bugzilla site (bugzilla.mozilla.org) to check whether it's a known, already-being-fixed issue.
Windows vs. Mac: Do the Crash Causes Differ?
Firefox is built and maintained for Windows, macOS, and Linux from the same underlying Gecko codebase, so the core troubleshooting logic in this guide — Troubleshoot Mode, extension conflicts, Refresh Firefox, hardware acceleration — applies identically on both platforms. That said, a few crash patterns skew differently by operating system, and it's worth knowing which side you're on before you spend time on a fix aimed at the wrong platform.
On Windows, the dominant cause we see is graphics driver conflicts, largely because Windows PCs run a much wider variety of GPU hardware and driver versions than Macs do, and Windows Update frequently reports a driver as "up to date" when a newer version is actually available directly from Intel, Nvidia, or AMD (a distinction that trips up even experienced users, as one of the comments below illustrates). Third-party antivirus conflicts are also a Windows-specific concern, since macOS's security model restricts the kind of deep process-hooking that causes many of these conflicts in the first place.
On Mac, crashes are more often tied to macOS version compatibility after a major system update, or to Rosetta 2 translation overhead on Apple Silicon Macs (M1 through M4) if you're running an older Intel-only build of Firefox rather than the native Apple Silicon version. Check whether you're running the correct build by going to Firefox menu > About Firefox — if it doesn't explicitly reference Apple Silicon and your Mac has an M-series chip, download the correct native build directly from mozilla.org/firefox for a meaningful stability and performance improvement.
Preventing Firefox From Crashing Again: A Maintenance Checklist
Once the immediate crashing is resolved, a small amount of regular maintenance keeps it from returning. None of these take more than a minute or two, and doing them monthly catches most new conflicts before they cause a crash:
- Review installed extensions quarterly. Go to
about:addonsand remove anything you no longer actively use — every extension is another process that can fail and another piece of code with access to page content. - Keep Firefox on auto-update. Confirm this at Settings > General > Firefox Updates > "Automatically install updates," and don't ignore restart prompts for more than a day or two.
- Restart Firefox at least daily rather than leaving it running continuously across many days, which lets accumulated memory and cached state clear out fully.
- Keep your graphics driver current. Set a reminder every 2-3 months to check for a GPU driver update directly from the manufacturer rather than relying solely on automatic OS updates, which often lag behind.
- Check about:crashes after any new software install — VPN clients, PDF printers, and download managers sometimes install browser components without clearly asking, and a fresh crash entry right after an install is a strong clue.
If you manage Firefox across several family or office computers, applying this checklist proactively rather than only after a crash happens is worth the small time investment — most Firefox crash tickets we handle at IT Cares trace back to a graphics driver that was many months out of date, or an extension installed once for a single task and then forgotten entirely. On a small office of 5-10 machines, fifteen minutes of quarterly maintenance is considerably cheaper than the lost productivity from even one employee losing work to a mid-task browser crash, and it folds naturally into a broader managed IT routine if you'd rather not track it manually.
One more habit worth building in if you regularly lose unsaved work to a crash: enable Firefox's Session Restore feature explicitly rather than relying on it only kicking in automatically. Go to Settings > General > Startup, and set "When Firefox starts" to "Show your windows and tabs from last time." This doesn't prevent crashes, but it means that when one does happen despite your best maintenance, your open tabs (though not necessarily unsaved form data typed into a webpage) come back automatically on the next launch rather than forcing you to reconstruct your browsing session from memory or bookmarks.
Firefox Still Crashing After Trying These Fixes?
IT Cares offers same-day remote troubleshooting for Windows and Mac: profile corruption, driver conflicts, antivirus interference, and full system diagnostics. Most Firefox crash cases resolved in one session.
Frequently Asked Questions
Why does Firefox keep crashing?
Firefox crashes are most commonly caused by a misbehaving extension, hardware acceleration conflicts with your graphics driver, a corrupted user profile, or an outdated build. Start with Troubleshoot Mode (Help menu > Troubleshoot Mode) since it disables extensions and hardware acceleration at once, telling you within minutes whether the cause is add-on related or something deeper.
What is Firefox's Crash Reporter and should I send reports?
When Firefox crashes, it offers to send a report to Mozilla with technical details about what was happening at the time of failure. Sending these is safe, doesn't include browsing history or personal data by default, and directly helps Mozilla identify and patch widespread crash bugs faster.
Will Refresh Firefox delete my bookmarks and passwords?
No. Refresh Firefox (via about:support) preserves bookmarks, browsing history, passwords, cookies, and autofill data while removing extensions, themes, and settings that might be causing instability. Firefox also backs up your old profile to the desktop automatically before refreshing.
Is Firefox crashing more since a recent update?
It's possible — Mozilla ships a new version roughly every 4 weeks, and occasional regressions get through. Check your version at about:firefox and compare against when crashing started. Consider temporarily switching to the Extended Support Release (ESR) channel, which prioritizes stability over new features.
Does Firefox crash more than Chrome or Edge?
There's no reliable data showing Firefox crashes meaningfully more overall — all major browsers share similar root causes (extensions, driver conflicts, corrupted profiles). Firefox uses Gecko rather than Chromium, so specific crash signatures differ, but site-specific crashes are a stronger signal than assumptions about the browser overall.
Why does Firefox crash only on certain websites?
Site-specific crashes usually point to a resource-heavy page triggering a hardware acceleration or memory issue, or an extension conflicting with that site's structure. Test with Troubleshoot Mode on that specific site — if it stops crashing, an extension is involved. Try Private Browsing too, to rule out cached data corruption for that domain.
Can too many open tabs cause Firefox to crash?
Yes, particularly with 8GB RAM or less and 40+ tabs open, which can exhaust available memory. Check about:memory for a detailed breakdown, and consider a tab-management extension like OneTab to consolidate inactive tabs rather than keeping them all live.
When should I stop troubleshooting Firefox myself and call a technician?
If Troubleshoot Mode and a Firefox update don't resolve the crashing within about 20-30 minutes of testing, it's reasonable to get professional help rather than continuing to profile rebuilds and system diagnostics yourself, especially on a work computer. A technician can typically isolate the exact cause in 10-15 minutes using diagnostics that take much longer to interpret correctly alone.
Comments (3)
Troubleshoot Mode is such an obvious fix in hindsight but I never knew it existed after using Firefox for probably 10 years. Turned out to be an old VPN extension I hadn't opened in months. Removed it, everything's been stable for a week. Wish I'd found this guide before spending an evening reinstalling Windows drivers for nothing.
Had the profile corruption issue — Refresh Firefox fixed it in under a minute and kept every single bookmark and saved login exactly like the article said. Was nervous to try it but the automatic backup folder on the desktop made it feel safe. Should have tried this before the new profile route, would have saved some time.
Called IT Cares after Firefox was crashing on literally every launch for two days straight. Technician found it was an outdated Intel graphics driver in about 10 minutes on a remote session, something Windows Update kept saying was current. Fixed permanently, and he explained why hardware acceleration was the trigger. Good value for the price.
Leave a Comment