Package Details: thorium-browser-bin 122.0.6261.132-1

Git Clone URL: (read-only, click to copy)
Package Base: thorium-browser-bin
Description: Chromium fork focused on high performance and security
Upstream URL:
Licenses: BSD
Conflicts: thorium-browser
Provides: thorium-browser
Submitter: StarterX4
Maintainer: xiota
Last Packager: xiota
Votes: 31
Popularity: 4.77
First Submitted: 2022-08-03 14:39 (UTC)
Last Updated: 2024-03-16 02:10 (UTC)

Pinned Comments

xiota commented on 2024-02-09 01:30 (UTC) (edited on 2024-02-10 05:08 (UTC) by xiota)

This package now uses the SSE3 version because benchmarks on my computers show no performance benefit from using the AVX/AVX2 versions.

xiota commented on 2024-01-18 04:21 (UTC) (edited on 2024-02-21 09:22 (UTC) by xiota)

I made alternate PKGBUILDs: SSE3, AVX, AVX2. (makepkg -p PKGBUILD.avx2)

However, there is no point making dedicated packages for each because there is no performance benefit from using different versions.

The "normal" version ("AVX") does reference avx2 in the config, but the exact compiler flags are unspecified. All 64-bit versions contain AVX and AVX2 instructions. So too do the Chromium binaries from the official Arch repos. Chromium-based browsers probably detect processor capabilities at runtime, so attempting to target specific instruction sets would not be expected to significantly improve performance.

Here are my results from speedometer 2.1, using fresh profiles:

  • SSE3: 83.8±1.0
  • AVX: 83.8±1.0 (not a mistake, SSE3 and AVX had identical results)
  • AVX2: 83.6±1.9

xiota commented on 2023-10-10 04:01 (UTC) (edited on 2024-02-10 05:06 (UTC) by xiota)

  • This is an autoupdating package that attempts to download and package the latest version available.

    • Rebuilding should be sufficient to package new releases.
    • Check that there is actually a new release at Alex313031/thorium.
    • To make the declared version, set environment variable _autoupdate=false
  • Avoid flagging and commenting at the same time for the same issue.

    • Flag for common issues with standard solutions.
    • Comment for issues requiring explanation or debugging.
    • Use a pastebin for blocks of text more than a few lines.

Latest Comments

1 2 3 4 5 6 Next › Last »

xiota commented on 2024-04-10 03:01 (UTC) (edited on 2024-04-10 03:04 (UTC) by xiota)

There is no need to change any of the PKGBUILDs unless something is broken because they all attempt to use the latest available version. To see this:

$ grep '^pkgver=' PKGBUILD*
$ makepkg -Cdop PKGBUILD.avx2
$ git diff -- PKGBUILD.avx2

The -bin suffix is required for AUR packages of this type. The sse3/avx/avx2 identifiers distinguish the packages from each other and prevent conflicts. This way, building a different version does not overwrite the package from another version, and they can all be installed simultaneously for benchmarking.

I switched this package to the SSE3 version because, as far as I can tell, all chromium-based browsers contain and use AVX2 instructions when supported by the processor.

You can see that all of them contain AVX2 instructions with aur/intelxed. To demonstrate with extra/chromium:

$ xed -i /usr/lib/chromium/chromium | grep AVX2 | head

So why use this package instead of another? The binaries were built with profile-guided optimization, which improves performance by about 15-20%. Most packages that build chromium from source have PGO disabled. Building with PGO and debugging failures is extremely time consuming.

kersh commented on 2024-04-09 22:06 (UTC)

Hello. I've recently commented here on switching AVX2 repo from main one to AVX2 special, however it has become a public archive from 2024-02-22 and as far as I can see you have reflected these changes in your PKGBUILD.avx2 as well. But according to this post all builds are now in the main repository so you can keep pkgver variable in all of your PKGBUILD files equal (which now should be 122.0.6261.132)

I also have a question about weird in my opinion naming scheme: pkgname variable in your PKGBUILD adds "-bin" to the end of default package name and due to _pkgname also adding hardware extension postfix it turns into some terrible mess. Why not just name it "thorium-browser" for all versions? A vast amount of AUR and Arch packages use these naming scheme where you have "<name>" version for stable releases and "<name>-git" version for top of trunk ones. I see absolutely no reason to have any other package name than just "thorium-browser".

Again, it is not a very complicated task to just change PKGBUILD files content on your own, however it is pretty annoying doing so each time you want to update the package.

Thank you for your work. Despite all my complaints it is still a great repository.

enihcam commented on 2024-04-05 15:58 (UTC) (edited on 2024-04-05 16:13 (UTC) by enihcam)

Regarding AVX2 performance, it's really up to the scenarios (e.g. WebAssembly, WebRTC, WebGPU etc.) and the CPU model you are using. Most modern CPUs have AVX2 instrument built-in. Enabling AVX2 simply does not harm. For those who don't have AVX2 can just use chromium.

josete commented on 2024-02-24 12:21 (UTC)

Thanks a lot for the information and the fantastic work with these AUR packages. I really mean it!

xiota commented on 2024-02-23 21:21 (UTC)

@josete That is another type of "popup". Unfortunately, it's an overloaded term. I have no problems creating bookmarks.

ArchWiki page about AUR has a lot of information. In short, you can make and install the package with the following commands:

git clone
cd thorium-browser-bin
_pkgver=120.0.6099.235 makepkg
sudo pacman -U thorium-browser-bin-120.0.6099.235-1-x86_64.pkg.tar.zst

Adjust the commands according to the package and what you are trying to accomplish.

josete commented on 2024-02-23 21:01 (UTC)

Maybe what I call a popup screen is something else. One example is the button "Add this page to bookmarks" (I think that's the right name). A very little screen shows up asking for the right place to store the bookmark. Right there the system crashes. Anyway I'd like to go back to the previous version but I don't know what to do with this ... "_pkgver=120.0.6099.235 makepkg". My knoledge in Linux is still very limited. I guess I'll find it in the Archwiki. Thanks!

xiota commented on 2024-02-23 20:36 (UTC)

@josete I am unable to reproduce your issue after visiting top several search results for "popup test" on Arch, Plasma, X11. However, another Manjaro user previously reported a system lockup.

Try searching for related issues at Alex313031/thorium/issues. If you don't find anything, you can consider opening a new one.

josete commented on 2024-02-23 16:36 (UTC)

When a popup screen shows up, the whole system crashes. My system is Manjaro Plasma. Does anybody else have the same problem?

xiota commented on 2024-02-23 08:38 (UTC) (edited on 2024-02-23 09:27 (UTC) by xiota)

There's an issue with profiles that causes segfaults in 121.0.6167.204. All SSE3/AVX versions are affected. If you didn't save a copy of the previous version, it can be rebuilt by running:

_pkgver=120.0.6099.235 makepkg

Since not all users are equally affected, I am not downgrading the package for now. (But will reconsider if more problems are found.)

yaakoss commented on 2024-02-23 08:23 (UTC)

@xiota I also tried the binary directly from thoriums repo. The same error happens, no matter what version. (sse3/avx or even AppImage) There are already two issue reports regarding this issue. I added the last parg of gdb output to my issue report on github.