Brave Crashing/Not Responding

Hi all,

Recently brave has been crashing/not responding to almost every action.

I originally had the issue when restoring tabs. I opened brave like normal and went to restore all my tabs from my previous session, and this results in the browser freezing and not responding. Closing with task manager and re-opening the browser to perform the same actions replicates the freeze. Additionally, I have some groups saved which vary in tab size (from 1 tab to ~15). Opening any group from the top bar under the search bar replicates the crash.

I can get brave to run if I just open a new instance of it. It has been able to run 10-20 new tabs. However, even when running just one tab, I notice that there is significant latency/lag with typing in the search bar. It’s as if I’m typing in 15fps. On the new tabs, nothing else seems to be compromised in terms of speed, and I don’t have any connectivity issues with my regular browsing.

For reference, I am running on windows 10. I have tried some of the recommended tricks, i.e. Restarting my computer, turning off all extensions, turning off (and on) hardware (graphics) acceleration, deleting all my browser data (cookies, history, etc.), uninstalling and reinstalling brave, all to no avail. This all seemed to happen after the recent update. I am on this build (copied from the about brave section):

Brave is up to date

Brave 1.86.139 (Official Build) (64-bit)

Chromium: 144.0.7559.59

Some misc. things to note:
-I run vertical tabs, but I haven’t had the crashing issue with those like the other forum posts mention. The issue seems to persist when I open multiple tabs at once or fetch tabs via. restoration.

-I’ve run brave beta and that seems to run pretty smooth. I don’t have any of the same latency in the search bar that I do with this recent build of normal brave. Also, running normal brave in incognito mode is also pretty smooth. I’m unable to replicate the crashes on brave beta. I have made groups with ~15 tabs, closed brave beta with task manager, reopened it and restored tabs, and it was fine. Restoring the group from the top bar was fine as well. However, I have been able to replicate the crash on normal brave → incognito mode, following the same procedure.

In further testing just now, the normal browser won’t even load up anymore. Every time I start it up it’ll just be grey and not responding. I’m not sure what I did to cause this, and uninstalling and reinstalling the browser doesn’t fix the issue.

I’m experiencing similar issues. For me, these issues popped up just yesterday, 1/17/26. I haven’t tested incognito, but the freezing/crashing on regular tabs (or even just opening Brave) is on par with what you’re experiencing too. Currently running the latest version of Brave 1.86.139 (Official Build) (64-bit) It also might be important to state that I’m running Brave on Windows 11. All attempts to restore the browser, clean cache, uninstall → reinstall, disable hardware acceleration lead to no changes or fix.

Possibly related to - read on down through the post and replies at:

Brave "not responding" when I try to close a tab

for the play by play. Somewhere along there, you will also find:


@Mattches

With Brave Browser updated to v1.86.139 → the problem above (Brave crashing, not responding).

And, I am guessing it is related to the problem at:

Browser keeps freezing when I try to close a tab

Also, a fix/workaround, by @morevo below:

Brave Crashing/Not Responding - #7 by morevo

Thanks for linking the post.

Something additional I wanted to add, though I don’t know if it’s related to normal brave:
I’ve been using brave beta as a replacement, and I’m getting some crashing there. It has only happened over some sustained use, maybe ~30min or longer of a session. It has only crashed once around ~5min in. It doesn’t seem to crash for any particular reason. Also, upon reopening brave beta, it can restore tabs just fine. I’m also not getting any search bar latency the moment before a crash. I have about ~20 tabs open, enough to make the vertical tabs scroll. Not sure if that’s relevant, but given the vertical tabs conversation, I thought I’d throw that in there.

Had a few more crashes happen in quick succession, they seemed to be all caused by closing tabs. Specifically, I close tabs via. ctrl + W. The browser is pretty unusable at this point, given that I have to restart it and restore my tabs every few minutes.

I encountered a severe issue after updating to the latest stable version: I couldn’t launch the browser at all.

Before the update, I had around 40 tabs open with the “Continue where you left off” setting enabled. As a result, every time I tried to start Brave, it would freeze and crash immediately due to the load.

Since I couldn’t access the UI to change settings, I found a workaround. For those who are locked out of their browser, the temporary solution is to manually modify the Brave configuration file to force-disable the Vertical Tabs feature. This solved the crashing issue for me.

Here are the steps to do it (With the help from Gemini):

The Cause:
The Vertical Tabs feature has been broken due to upstream modifications in Chromium, combined with a lack of adequate checks and consideration by the Brave team when merging these changes. Consequently, using Vertical Tabs with a large number of open tabs causes the browser to freeze or crash.

For users who can still open Brave:
If you are currently able to launch the browser but experience crashes when attempting to restore a previous session with multiple tabs, or when closing a single tab while many are open: Please go directly to Settings > Appearance and uncheck “Use vertical tabs”.

For users who cannot open the browser at all:
If you are locked out because the browser crashes instantly on launch (like in my case), the temporary solution is to manually modify the Brave configuration file to force-disable the Vertical Tabs feature. Here are the steps:

Step 1: Ensure Brave is Completely Closed

Make sure there are no Brave processes running in the background. Check your Task Manager (Windows) or Activity Monitor (macOS) to be sure.

Step 2: Locate the User Data Folder

Navigate to the directory where Brave stores your user profile.

  • Windows: Press Win + R, paste the following path, and hit Enter:
    %LOCALAPPDATA%\BraveSoftware\Brave-Browser\User Data\Default\
  • macOS: Open Finder, press Cmd + Shift + G, and enter:
    ~/Library/Application Support/BraveSoftware/Brave-Browser/Default/
  • Linux:
    ~/.config/BraveSoftware/Brave-Browser/Default/

(Note: If you use multiple profiles, the folder might be named Profile 1, Profile 2, etc., instead of Default.)

Step 3: Backup the Configuration File

Find the file named Preferences (it has no file extension).
Crucial: Copy and paste this file to a safe location (e.g., your Desktop) as a backup. If you make a syntax error in the next steps, you can restore this backup to avoid losing your data.

Step 4: Edit the Preferences File

  1. Open the Preferences file with a text editor (Notepad on Windows, TextEdit on macOS, or a code editor like VS Code).

  2. The file contains a long string of JSON text. Use the “Find” function (Ctrl + F or Cmd + F) to search for the keyword:
    "vertical_tabs"

  3. You should find a section that looks something like this (it might be compacted into one line):

    "brave": {
       ...
       "vertical_tabs": {
          "enabled": true,
          ...
       },
       ...
    }
    
  4. Change "enabled": true to "enabled": false.

Step 5: Save and Relaunch

  1. Save the file and close the text editor.
  2. Launch Brave.
  3. The browser should now open with standard horizontal tabs, which should resolve the freezing issue caused by the vertical tab rendering on startup.

Hope this helps!


Q: Why was I able to use Vertical Tabs before? / Why does it crash sometimes but not others?

A: According to ongoing discussions on GitHub (which are not yet fully verified), the root cause seems to be linked to the scrolling mechanism of the Vertical Tabs sidebar.

  • The Trigger: The crash appears to occur when the sidebar contains enough tabs to become scrollable (or when closing a tab causes the list to scroll/adjust). This implies that the threshold for the crash may vary depending on your monitor resolution, display scaling settings, and the number of tabs open.
  • The Timeline: This explains why you might have been able to launch the browser successfully at first. With fewer tabs, the sidebar doesn’t need to scroll, so the browser remains stable. As you browse and accumulate more tabs, opening them might not crash the browser immediately. However, the moment you attempt to clean up or close a tab, the sidebar tries to adjust the view or scroll, triggering the bug and causing the freeze/crash. This leads to the common report: “My browser crashes as soon as I close a tab.”
  • Startup Crashes: When using the “Continue where you left off” feature, Brave attempts to load all your previous tabs simultaneously. If you have many tabs, this immediately forces the sidebar into a scrollable state, triggering the bug instantly upon launch.
  • Pinned Tabs: Specifically, if you use Pinned Tabs, it has been observed that the vertical sidebar might enter a “scrollable” state even with very few tabs open (which seems to be a separate UI bug). This can prematurely trigger the main crash issue.

Disclaimer: This bug is still under active investigation. The details above are a summary of community observations from GitHub issues and may not perfectly reflect the technical reality in every case. However, the bottom line remains: The only reliable workaround for now is to temporarily stop using Vertical Tabs.

thanks, this solved the issue, but it has made my browser a mess since I’ve around 50 tabs grouped for different scenarios. hope they’ll fix it soon

SInce around 16th January Brave browser (v.144.1.86.139 on Windows 11 v.25H2 2600.7623) randomly but frequently “stops responding”. If I force restart and choose option “Restore pages” it instantly “stops responding”. I use verticial tabs. If Brave no longer supports vertical tabs then I’ll have to stop using it.

@morevo

You have helped many people; thanks.

Hi there, I came to confirm this exact issue. Oddly enough, I had two “windows’“ accounts running to circumvent microsoft’s need to look up ny butthole, and the ‘restore last session’ crash usually only occurred on the pants down side of the machine (the show model, for downloading programs that need to be officially signed from the micrksoft store)

\\EDIT \\\2* this may not be the same issue, but to leave this note for #yeolescroll , the account suffering the crashes was using the newer size configuration. Also, ya’lls tabs are about to finish the border wall, but by alk means, if you like tying up all that memory, in your browser, and your head, keep on keepin on bud.

i see this waa also edited a few days ago, so I think we’re warm here, but Ive been wrong once before, I’d love to know what was csusinng that.. And I know I was f*cking around heabily at the time to pwn microsoft for those windows 10 out of support threats. Mission accomplished. And they gave me a 1997 clippy.gift lol.

The other repeat variable I noticed , is that i was usually looking internally at my local network, and externally, in the same browser window or group when then INITIAL crash occurred. After that, that window or group crashed every single time. So it was my assumption at the time that this has something to do witb chromium changing the way you can access internals. Furthermore, the way frames are handled is chsnging with thjs. Im on mobile, and I havent used my “windows” laptop in months so I dontt remember what those rules are called at the moment, but I know I was able to flatline Edge in simiilar fassion. And, at that point I gave up probing, because I didnt want to cause a turf war with microsoft, and I returned to the my other account.

My thoughts for now are to change your settings to initialize brave with a custom url or braves startpage, becsuse you csn still elect to restore that session if youre tryjng to debug. I’ll look for the local access rules but if i forget, giggles™️ developer news will hsve them..

Can confirm having this issue as well. Do we need to track the issue in Github or here to be notified when this bug is fixed?

I would suggest trying to install Brave on a fresh windows install on a different machine and see if you have the same problems. If the problem is gone on the new machine then it is likely something wrong with the file system or windows.

If you have the same issue on new hardware and new copy of windows then the problem is Brave or incompatibility with windows update. Some windows system calls are very odd and difficult for seasoned programmers to wrap their head around especially if Brave is doing anything low level.

If you have succes on the new machine you could try migrating your Brave settings to the new machine. If it starts crashing that profile may have some sort of corruption.

brave also stores a lot of cache data you may want to also try emoting that from the profile if you have problems.

I’m having the same problems since December. Brave will go catatonic after posting on social media. The title bar will change to a generic Windows title bar with “not responding” in it. It makes Brave very hard to use as I have to wait 10-12 seconds after any posting action for responsiveness to return.