Brave crashing on Mac immediately after opening

@leot7 can you confirm your version and share the Crash Report IDs which can be found at Brave://crashes, it’s the number ending in 00000000. Thank you!

Brave doesn’t open at all, so I’m not able to access Brave://crashes as far as I’m aware. Similarly, I can’t access the version number within Brave because it crashes immediately. When I right click on the Brave icon within the download .dmg, what is listed as the version is 153.1.95.104.

@leot7

Your crash report - from which you posted some lines - will also have the Brave Browser (“BB”) version.

Also, to get the BB version - using the Terminal.app:

defaults read /Applications/Brave\ Browser.app/Contents/Info.plist CFBundleShortVersionString


Attempt to launch BB.

Then, in the Terminal window:

log show --last 5m --style compact --predicate 'eventMessage CONTAINS[c] "Brave" OR process CONTAINS[c] "Brave" OR subsystem CONTAINS[c] "Brave"'


And:

Console.app → Reports → Crash Reports/Diagnostic Reports may contain a Brave Browser...ipsreport. Apple notes that Console exposes these reports separately from the live log.


Time frame: from roughly 30 seconds before through 30 seconds after the failed Brave launch.

Thanks for the report! Dug into this further, and I don’t think it’s the same issue as #49861 after all. (For the crash itself: only Thread 0 — the one marked “Crashed” — is what actually caused it, so that’s all that’s needed; the other threads (0-37) are just normal background threads captured at that moment, not separate errors.)

That report (fixed via brave-core#31609) was on Brave 1.83.108 / Chromium 141, and it was already closed as fixed a long time ago. Your “Brave Version” field (153.1.95.101) corresponds to Chromium 153 — roughly a year of Chromium releases later — so that fix would already be included in your build well before this happened. Combined with what you noted (all profiles crashing for you, vs. just one profile in that other report), this looks like a different, currently unidentified crash rather than a recurrence of #49861.

Nothing else needed from my side for now — the Exception Type + top frames you sent covers what I was trying to check against #49861. The one limitation is that your trace doesn’t have symbol names (just raw offsets), so I can’t pin down the actual crashing function without a symbolicated build. If you want to push this further (optional, not required): check whether Brave’s automatic crash reporting is enabled on your end — if so, this crash may have already reached Brave’s crash server with full symbols, and flagging it directly to Brave support with the report’s timestamp/UUID could let them look it up on their side.

@asdfg can you confirm your current version that’s crashing? Please share your Crash Report IDs which can be found at Brave://crashes. It’s the number ending in 00000000. Thank you!

I updated to Brave 1.96.59 and it is still happening. The Uploaded Crash Report ID is: 17a70200-291f-6a10-0000-000000000000.

Thanks!

Thanks @cap296 for confirming. A few follow up questions which will help us to narrow the root cause down:

  • Any new extensions?

  • Does the crash occur in a fresh profile? Private window?

  • Any specific steps that reliably lead to the crash? Is it happening every time or intermittently?

Thank you for any additional info!

Several of us have noticed Brave crashes on Macos starting with v195 and continuing to the latest release (including Beta builds). The cause seems to be custom application keyboard shortcuts, which you see from either:

  • System Settings → Keyboard → Keyboard Shortcuts → App shortcuts
  • defaults read -g NSUserKeyEquivalents

This is discussed here: https://github.com/brave/brave-browser/issues/59097#issuecomment-5821316635

Thanks for the follow up. Here’s what I got:

  • No new extensions have been added. I’ve tried disabling all extensions after a fresh reinstall and it still crashes.
  • It doesn’t seem to crash as often in a private window but I can’t say for certain. (that’s a hard action to try since it usually crashes before I can test it.) The crash occurs in both my personal profile, a new profile, and as a guest. It is also very hard to start a new profile though because:
  • There are a few specific steps that will always crash the browser. I’ve noticed three consistent actions that never fail at producing a crash although it certainly feels like there are probably other related actions that will trigger it as well. My observations, however, include 1) selecting “restore pages” if that pops-up after a previous crash. 2) trying to start a new profile OR selecting a profile if the pre-cursor/profile switch window is enabled. 3) exporting or importing anything (for example exporting bookmarks; I can open the manager, select the more/extra button, and get all the way to choosing the location to save the bookmarks, but once I click “save” it crashes and the file does not save).

I hope this reads in at least a semblance of a linear fashion.

@cap296 Do you have any global keyboard shortcuts configured in

  • System Settings → Keyboard → Keyboard Shortcuts → App shortcuts

?

Thanks for the help, and sorry for the late reply. I definitely would like to push this further because I would really like to get Brave working again.

How would I make sure Brave’s automatic crash reporting is enabled if I am unable to open Brave at all? Is there a way to enable this? I’d love to have the issue flagged with Brave support so that it can be fixed.

@leot7 @cap296 we’ve just release 1.96.60, can you let me know if you’re still experiencing the crash after updating?

Thank you

leot7, since Brave crashes before it even opens, brave://crashes won’t be reachable (that requires the browser to actually run). There are two independent, documented ways to get crash data without needing the app open:

  1. Brave’s own crash reports (Crashpad), per Brave’s support article (“How do I manually submit crash reports?”):
    ~/Library/Application Support/BraveSoftware/Brave-Browser/Crashpad/completed/
    Look for .dmp files there.

  2. macOS’s own system-level crash reports, via the Console app (separate from Brave, per Apple’s own Console guide): open Console.app → sidebar → Reports → Crash Reports. These are .ips files. If you’re on an admin account you’ll see all reports, not just yours. You can also right-click a report → “Reveal in Finder” to grab the file directly.

Grab whichever of these you find (ideally both, matching the timestamp of a recent crash), and share them either here or on the GitHub issue tracker (github.com/brave/brave-browser/issues).

A couple of details that would help the devs narrow it down faster: what macOS version you’re on, whether it’s Intel or Apple Silicon, and whether the crash also happens in a brand-new macOS user account (that tells them whether it’s specific to your Brave profile or something broader on your system).

Sources:

@steeven I have re-installed Brave with version 1.96.60 and it is still crashing immediately upon opening.

@MA1290 I have uploaded the .dmp file to the GitHub (I was unable to attach .ips to the GitHub and couldn’t attach either here). As far as the other information, I am on MacOS Tahoe 26.6.2 with an Apple M3 Pro chip. The issue is linked here.

leot7, thanks for the update and for filing #59537 with the .dmp attached. Since it reproduces easily and there’s now a proper report upstream, that’s probably the right place for the Brave team to pick this up from going forward. Hope it gets resolved soon.

@leot7

Your binary crash dump .dmp file (at your Brave GitHub post) - unraveled now, as an ordinary text file brave-dump.txt - and any text editor can open:

brave-dump.txt (164.7 KB)

Very brief snapshot:

OS: macOS 26.6.2
CPU: arm64
Process: Brave
Crash: EXC_BREAKPOINT / EXC_ARM_BREAKPOINT
Uptime: 7 seconds
Thread: CrBrowserMain
PC: Brave Browser Framework + 0x4358b2c


Suggest, go to: ‘Brave Crashing Immediately - #11 by Mattches’ and study that reply, and each subsequent reply, by @Mattches of Brave Support.

Hi there,

I updated to 1.96.60 and yes the crashes continue.

I checked and yes there are shortcuts listed under Brave Browser.

This is most likely the problem (or at least one of them). A change in Brave introduced in v195 does not read the macOS keyboard shortcuts safely and leads to a crash. The Github issue I linked above has more details by @sanalsanu83 and a workaround for the time being (i.e. deleting the global keyboard shortcuts, which is unacceptable for me).

Thanks all, it looks like this issue is directly related to what’s being reported https://github.com/brave/brave-browser/issues/58699. The team is aware of it and reviewing.