Segmentation Fault

[MulverineX]

System Details

• OS: Windows 11 w/ Atlas playbook
• Hardware: i7-10750H, 16GB memory, RTX 2070
• Thorium Version 121.0.6167.204

Problem
After updating to 121 from 119 Thorium refused to run, and through the terminal I got simply Segmentation Fault.

Also a side note, to downgrade I had to download the release zip and replace manually, the mini installer wouldn't downgrade.

[gz83]

I don't encounter this error, in which version did you encounter this error (AVX, AVX2 or SSE3)?

@MulverineX

[MulverineX]

@gz83 I tried all 3 versions; manually replacing from the release zip files

[gz83]

Please tell me the specific process of reproducing the problem and I will try to see if I can reproduce the problem you encountered.

@MulverineX

[MulverineX]

• Have 119 installed
• Use https://github.com/Alex313031/thorium-winupdater/releases/tag/1.8.1
• Seg faults
• Unzip the BIN directory of any of the release types into your installation folder
• Seg faults regardless of type

[Alex313031]

@MulverineX I tried all the versions in a Win 10 VM, and had no problems. Also @gz83 is using Win 11 too.

[MulverineX]

Very strange, is there some way for me to get additional debug information?

[gz83]

Skip winupdater and completely delete the original installed version, then install version 121 to see if you still encounter errors.

@MulverineX

[MulverineX]

It appears that after restarting the computer and the update service running again, the browser is updated with no issues, very strange

[MulverineX]

Aaaand it's broken again

[AnuRage-git]

I've been getting the same Segmentation fault issue on Linux though. My Windows version works perfectly fine. Only issue is Netflix playback where it gets stuck in a clear cookies loop but it could be a Netflix issue too

[dmolin]

I can confirm segmentation faults with the latest version of Thorium (121.0.6167.204) in Linux (Manjaro):

[25671:25671:0222/083138.137568:ERROR:atom_cache.cc(224)] Add _ICC_PROFILE_1 to kAtomsToCache
[25671:25671:0222/083138.137638:ERROR:atom_cache.cc(224)] Add _ICC_PROFILE_2 to kAtomsToCache
[25671:25671:0222/083138.143403: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-management` command line flag to enable it if you are not using the official Google Chrome build.
[0222/083138.182289:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0222/083138.182658:ERROR:elf_dynamic_array_reader.h(64)] tag not found
Segmentation fault (core dumped)

[Yaakoss]

The issue is caused by the profile manager. Thorium crashes if there are Profiles that have been added in the previous versions or if you add a new profile.
There is a workaround if you need multiple profiles.
You can create a new separate directory for each profile you use using the --user-data-dir parameter. At least on Linux this works.

[dmolin]

@Yaakoss yes, I noticed. In particular, I noticed that the issue was located in the "Local State" file but I was unable to pinpoint what exact part of it triggers the core dump.
For the moment I'm back to Chromium, that works just fine using the copy of my thorium config folder as-is, with all my bookmarks, profiles etc in place

[ThatMarko]

+1 for this error on latest KDE Neon (Ubuntu 22.04)

thorium-browser
[603862:603862:0226/170154.952517: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-management` command line flag to enable it if you are not using the official Google Chrome build.
[0226/170154.985916:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0226/170154.986036:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0226/170154.987524:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0226/170154.988580:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0226/170154.991592:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0226/170154.991652:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0226/170154.992615:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[1]    603862 segmentation fault (core dumped)  thorium-browser

[MarceloEmmerich]

Same issue on Arch:

The fastest browser on Earth.
[29948:29948:0227/080452.437094: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-management` command line flag to enable it if you are not using the official Google Chrome build.
[0227/080452.558610:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[1]    29948 segmentation fault (core dumped)  thorium-browser

[federerfanatic]

I downgraded to version 120.0.6099.235-1 and used apt-mark to hold it.

[federerfanatic]

I downgraded to version 120.0.6099.235-1 and used apt-mark to hold it.

Ok. I now have installed the latest version. I was having problems with the nvidia driver. Advice: reboot machine
and do not pick the special options menu item in the boot menu. Just boot normally. I had installed the kernel headers files during the boot process as the desktop was not coming up. It came as the build was finishing but I neglected to reboot from scratch. If nvtop can not access the gpu despite the desktop being supposely running then you really should reboot.

[federerfanatic]

The latest version 121.0.6167.204-1 works on ubuntu-22.04 amd 64 running Xorg.

[daggerwolf45]

I have the same issue. I'm on Arch running Linux 6.7.6. Downgrading to 120.0.6099.235-1 fixed it for me as well.

[mindrunner]

I can work around this issue by selecting a user profile on startup (skipping the profile manager)

thorium-browser --profile-directory=Default

[sohanglal]

I can work around this issue by selecting a user profile on startup (skipping the profile manager)

thorium-browser --profile-directory=Default

Related #596

[Alex313031]

@MarceloEmmerich @dmolin @mindrunner @ThatMarko @MulverineX Fixed in latest M122 version.