Alex313031
Thorium crashes on launch
System Details
- OS: MacOS Sequoia 15.5
- Thorium Version: M130.0.6723.174 - 10th Release
Problem Thorium all of a sudden crashes when launching. Running thorium with --disable-sync though seems to work Crashes with these errors/warnings:
[5613:38915:1003/163920.008294:ERROR:registration_request.cc(291)] Registration response error message: DEPRECATED_ENDPOINT [5613:42243:1003/163921.044758:FATAL:check.cc(363)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry! [1003/163921.051817:WARNING:process_memory_mac.cc(94)] mach_vm_read(0x16d0e4000, 0x8000): (os/kern) invalid address (1) [1003/163921.436172:WARNING:crash_report_exception_handler.cc(235)] UniversalExceptionRaise: (os/kern) failure (5) [1] 5613 trace trap ./Thorium
Also either with --disable-sync or without, i get this error:
Error: unrecognized flag --enable-external-memory-accounted-in-global-limit Try --help for options
Additional Notes Funny thing is it started this behaviour today, while thorium was open and working fine for hours. then all of a sudden it crashed and has been doing so ever since
[EDIT]: On my windows 11 desktop, thorium works perfectly fine
Having the same issue. Just started around an hour ago for me.
Downgraded to Thorium 124 and it seemed to work until I signed in with my google account. Now that version is broken in the same way, so I assume something about the google sign in is breaking suddenly.
I'm having the same issue. I was able to remove my profile, which allowed me to keep using the app as long as I don't attempt to sync my google account. If I attempt to sync my account Thorium crashes.
Having the same issue here. On Windows 10 and 11 laptops, no issues were encountered. However, issues were encountered on macOS Sequoia 15.7.
M2 macOS Sequoia 15.1.1 (24B91) thorium crashes when unlocking "Chromium Safe Storage" in your keychain. 'deny' allows thorium to load, then logging in to any google service will then crash.
I too am facing the same issue when running M130.0.6723.174 - 10th Release on Sequoia 26.0.1.
I'd faced this issue on an earlier version as well and downgrading to a previous version helped then.
I've downgraded to M126.0.6478.231 - 9th Release and it seems to be working well for me.
Edit: I've paused the sync with my google account
I have the same issue with Version 130.0.6723.174 (Official Build) (arm64) on Sequoia 15.5 (24F74). Using /Applications/Thorium.app/Contents/MacOS/Thorium --disable-sync works.
Thanks to @michaellammers for a better command:
open -a /Applications/Thorium.app/Contents/MacOS/Thorium --args --disable-sync
Same issue here. If there is no internet, Thorium won't crash. I guess it's related to google🤔
M1 MacOS Ventura 13.4.1 (22F82) crash on launch.
Confirmed --disable-sync works
I think evil-google does something. FUCK GOOGLE.
Same issue for Mac Pro M3 Sequoia 15.7. Thorium --disable-sync works for me.
Still crashing, I have to disable sync every single time just so it works.
FUCK GOOGLE!
Version 115.0.5790.172 (Official Build) (x86_64)
work for me Montery Mac os
Same!
As an addition to @chumbothewhale's excellent answer, the following also works and has a clean terminal exit
open -a /Applications/Thorium.app/Contents/MacOS/Thorium --args --disable-sync
I'm also experiencing this under Sequoia 15.7.1, and open -a /Applications/Thorium.app/Contents/MacOS/Thorium --args --disable-sync is a fine-enough workaround for the moment, so thanks to @chumbothewhale and @michaellammers.
Same thing for me.
Current workaround is opening it with the following command:
open -a /Applications/Thorium.app/Contents/MacOS/Thorium --args --disable-sync
99% sure google is messing around... AGAIN...
macOS 15.6.1 (24G90) Version 130.0.6723.174 (Official Build) (x86_64)
Same issue with me MacOS 15.6.1 (24G90) Macbook Air M1
only work open via CLI
open -a /Applications/Thorium.app/Contents/MacOS/Thorium --args --disable-sync
Thorium version https://github.com/Alex313031/Thorium-MacOS/releases/download/M130.0.6723.174/Thorium_MacOS_ARM.dmg
Is there any release in sight to fix this bug. Its anoying to start it via CLI all the time via --disable-sync! !!
Old chromium builds have this same problem but I downloaded the latest Chromium and it works without crashing so presumably it is a matter of rebuilding and updating.
On Wed, Oct 8, 2025 at 6:37 PM marab2 @.***> wrote:
marab2 left a comment (Alex313031/Thorium-MacOS#77) https://github.com/Alex313031/Thorium-MacOS/issues/77#issuecomment-3380891885
Totally agree with @jetonr https://github.com/jetonr
— Reply to this email directly, view it on GitHub https://github.com/Alex313031/Thorium-MacOS/issues/77#issuecomment-3380891885, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHCY7NL26EG56YGJX7J7733WTSO5AVCNFSM6AAAAACIGVTTBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOBQHA4TCOBYGU . You are receiving this because you commented.Message ID: @.***>
Its anoying to start it via CLI all the time via --disable-sync! !!
Automator -> New Application -> Run shell script -> /Applications/Thorium.app/Contents/MacOS/Thorium --args --disable-sync -> Export as Thorium No Sync.app.
You can also CMD+I on original app -> select icon -> copy -> CMD+I on new app -> paste icon, so it'll look the same in Dock/ Launchpad.
At least till fix is released this makes launching it not as annoying.
Has anyone recently built Thorium from the latest Chromium sources on macOS? I tried before but stopped due to very long fetch/sync times. If you’ve succeeded, could you share your exact steps (macOS/Xcode/depot_tools versions, key GN args, targets, and any workarounds for slow sync)? Also, if we end up with a reproducible recipe, would a maintainer be open to tagging/publishing a new release in @Alex313031 repo?
I’ll give it another go using the official guide and report back with logs/hashes: https://github.com/Alex313031/thorium/blob/main/docs/BUILDING_MAC.md
Currently, Thorium's codebase is insufficient to compile newer versions (above the current 132).
@bonakdarf92
@gz83
Hello, may i ask in which way Thorium on Mac will resolve this crush problem,
update to higher version of Chromium or just stay in current 132?
if update to higher version of Chromium,
there would have Manifest V2 to Manifest V3 update, and all V2 extensions will deprecated
this is the reason why i use Thorium， Thorium 132 is Manifest V2 extensions compatible and update disabled.
