You are not logged in.
Pages: 1
I cannot get Chromium (and both Google Chrome stable and beta) to display any page. Upon application startup it displays an error page reporting a SIGILL error. Starting from terminal I get:
[27506:27506:0308/111925.441373:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.Can someone please help me debugging this error?
Here is what I tried:
chrome --disable-gputhis gets rid of the error message, but not of the SIGILL error on the main window.
rm -rf $HOME/.cache/{chromium,google-chrome,google-chrome-beta} rm -rf $HOME/.config/{chromium,google-chrome,google-chrome-beta} rm $HOME/.config/chromium-flags.conf chromium --disable-gpu --disable-software-rasterizerI tried to decode crash dump messages but I might need a bit of guidance for that because I wasn't able to read them.
Some info about my system:
chromium --versiongives
Chromium 89.0.4389.82 Arch Linuxuname -rgives
5.10.21-1-ltspacman -Q | grep mesagives
lib32-libva-mesa-driver 20.3.4-3
lib32-mesa 20.3.4-3
lib32-mesa-vdpau 20.3.4-3
libva-mesa-driver 20.3.4-3
mesa 20.3.4-3
mesa-demos 8.4.0-4
mesa-vdpau 20.3.4-3pacman -Q | grep gpugives
xf86-video-amdgpu 19.1.0-2 pacman -Q | grep amdgives
lib32-amdvlk 2021.Q1.4-1
opencl-amd 20.45.1164792-4
xf86-video-amdgpu 19.1.0-2[EDIT] Add info about Chromium version and AMDGPU packages versions
Last edited by JamesStuck8 (2021-03-08 10:28:33)
Offline
Any suggestion?
Offline
Install https://archlinux.org/packages/extra/x86_64/mesa-demos/ and see if glxgears works.
And maybe provide some more details about your setup, e.g. is it X or Wayland?
Offline
Hi, thanks for answering. I confirm glxgears works. Few days ago I also successfully ran glamarks2. I think the problem is related to V8 because electron apps (Slack, Discord) and Google Chrome/Chromium stopped working.
I am in a X11 session on Gnome 3.38.4. I am using a 144Hz monitor if it matters. The GPU is a Radeon RX580 Nitro+, CPU is a Ryzen 2700x. Both are running at stock frequencies.
Offline
And I can confirm the same behavior using a Wayland session. To me it doesn't look like a X problem, otherwise more applications would be affected. Is anybody aware of anything going on with mesa? Any bug with V8? Are there config files I can check?
Offline
Maybe try starting it with "MESA_GLSL_CACHE_DISABLE=true".
Debian bug report: https://bugs.debian.org/cgi-bin/bugrepo … bug=918433
Offline
I occasionally get the same SIGILL error report while using webrtc within Chromium. Sometimes the tab wants a reload with this error reporting and other times the complete machine freezes. I use Chromium under xwayland and have an AMD GPU (Renoir APU, Ryzen 5 4650G). This behavior is all in all very frustrating.
I have tried to set "MESA_GLSL_CACHE_DISABLE=true" but the error message at the start
[547432:547432:0319/230937.865801:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.still persists. Also the freeze can still be triggered after some time in a video conference.
Offline
Well, I guess it's time to switch to Firefox then? The time-honored way of fixing intractable Linux problems: Just switch to something else until the bug is fixed.
Offline
I also tried your suggestion Morn but it didn't work.
I guess the switch to FF is a viable option (and it's how I am writing this comment
) but FF lacks multi profiles support (e.g. separate personal and work bookmarks, extensions and settings)... Also, chromium ditched profile syncing a couple of weeks ago and that's why I had to switch to Google Chrome.
Offline
Ok after quick googling I figured out how to have multiple profiles with FF. Game, set, match!
Offline
Pages: 1