search

Alex313031 / Thorium-MacOS

Thorium builds for MacOS (arm64 and x64).
https://thorium.rocks/
BSD 3-Clause "New" or "Revised" License
395 stars 6 forks source link

Application crash #45

Closed rohshall closed 4 months ago

rohshall commented 5 months ago

System Details

Problem The application fails to start. The error is: $ /Applications/Thorium.app/Contents/MacOS/Thorium [20364:259:0219/215433.033572:ERROR:policy_logger.cc(156)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(161) Cloud management controller initialization aborted as CBCM is not enabled. Please use the--enable-chrome-browser-cloud-managementcommand line flag to enable it if you are not using the official Google Chrome build. [0219/215433.320930:WARNING:crash_report_exception_handler.cc(235)] UniversalExceptionRaise: (os/kern) failure (5) Segmentation fault: 11

Screenshots NA Additional Notes NA

megaschatzi commented 5 months ago

Same here ...

deebakkarthi commented 5 months ago

Me too

midzer commented 5 months ago

Cannot reproduce with manually installed ARM .dmg from https://github.com/Alex313031/Thorium-MacOS/releases/tag/M121.0.6167.204

Had to use https://support.apple.com/guide/mac-help/apple-cant-check-app-for-malicious-software-mchleab3a043/mac though

Did you use the x64 version?

vtwinsf commented 5 months ago

Currently, I am using the ARM version without any issues. Moreover, my Mac is equipped with the M1 chip. I'm interested in finding out whether the OP is utilizing the x64 version.

rohshall commented 5 months ago

I get the crash on my M1 ARM Mac.

deebakkarthi commented 5 months ago

The older version downloaded from github works. But the latest version when installed via homebrew breaks.

along02 commented 5 months ago

It crashes when I try to add a profile.

gz83 commented 5 months ago

If the crash is caused by operating the new profile function, it will be fixed in the next version

10zero11 commented 5 months ago

I have also found this bug. My install is M1 Arm Mac, installed with homebrew.

It does appear to be caused by the profile selector code.

It can be successfully run as follows from a shell.

open -a "Thorium" --args --profile-directory="Default"

bland328 commented 4 months ago

I have also found this bug. My install is M1 Arm Mac, installed with homebrew.

It does appear to be caused by the profile selector code.

It can be successfully run as follows from a shell.

open -a "Thorium" --args --profile-directory="Default"

I have the same situation, installed via homebrew, but on an M2 MacBook Air.

After opening Thorium via the open -a "Thorium" --args --profile-directory="Default" suggested above, the first attempt to change profiles fails, though subsequent attempts do work.

Alex313031 commented 4 months ago

@rohshall @10zero11 @bland328 @vtwinsf Sorry guys, stupid mistake on my part. Fixed in latest M122 version.

rohshall commented 4 months ago

@Alex313031 thank you so much for fixing this. I tested the M122 version, and it is working beautifully! So, I am closing the issue.

10zero11 commented 4 months ago

thank you @Alex313031