You are not logged in.
Hi,
I'm not using chromium as my main browser, so the issue may be one week old without my noticing it.
When launching it, I get lots of ERRORS in console such as
[1882256:1882256:0618/102248.778134:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[1882229:1882250:0618/102249.100451:ERROR:client_native_pixmap_dmabuf.cc(218)] Failed to mmap dmabuf: Permission denied (13)
[1882256:1882281:0100/000000.519964:ERROR:native_pixmap_handle.cc(77)] dup: Too many open files (24)
[1890967:1890990:0618/104334.627517:ERROR:client_native_pixmap_dmabuf.cc(218)] Failed to mmap dmabuf: Permission denied (13)
as a result chromium finally opens but tehre is nothing in the 'head' zone, (url bar etc)
The only way I found to start it 'apparently' normally is to set MESA_GLSL_CACHE_DISABLE=true
Have I missed something in recent updates ?
What sould I check ?
thanks for any idea
SOLUTION
in my case a least, I had set "--enable-native-gpu-memory-buffers" in my "~/.config/chromium-flags.conf"
and completely forgot about it.
For some reason, it now crashes with my hardware and my setup.
Remove the flags, issue solved.
Last edited by squalou (2020-06-20 09:28:15)
Offline
additional info : 'google-chrome' from aur works.
Could be related to my profile / some settings ? no idea really, I dont use it much, can't remember customizing it
Offline
I'm having the same issue
using MESA_GLSL_CACHE_DISABLE=true with --disable extensions seems to cause a crash, but using the flag on MESA_GLSL on its own seems to work
Offline
Running Chrome with the --disable-gpu flag seems to allow chrome to start as well, although it looks like my previous attempt fix doesn't seem to have helped
It seems like turning off Hardware Acceleration seems to make it so neither the `MESA_GLSL_CACHE_DISABLE` or `--disable-gpu` are required
Last edited by ajayk111 (2020-06-19 07:08:45)
Offline
I use Chromium everyday. I have chromium-vaapi AUR on my laptops and official extra/chromium on desktop. All of them do not have the problem described here.
local/linux 5.7.4.arch1-1
local/chromium-vaapi 83.0.4103.106-1
local/mesa 20.1.1-1
Offline
The actual HW and mesa driver will probably matter, could be https://wiki.archlinux.org/index.php/In … ver_(i965)
Online
Hi,
tried both MESA_LOADER_DRIVER_OVERRIDE=i965 and / or MESA_GL_VERSION_OVERRIDE=4.5 (or other values)
No better result unfortunately :-(
Offline
As seen here : https://www.linuxquestions.org/question … 175677122/
I had this flag enabled
--enable-native-gpu-memory-buffers
it was set in
/home/my-user/.config/chromium-flags.conf
can't remember since when, years probably
removing this flag solves he issue, or works around it, as you prefer. I'm curious about the ventual performance issues related. (But again, it's not my main browser so for me, it's solved)
Offline
As seen here : https://www.linuxquestions.org/question … 175677122/
I had this flag enabled
--enable-native-gpu-memory-buffers
it was set in
/home/my-user/.config/chromium-flags.conf
can't remember since when, years probably
removing this flag solves he issue, or works around it, as you prefer. I'm curious about the ventual performance issues related. (But again, it's not my main browser so for me, it's solved)
Ditto for me. I suspect I had set this when trying to get hardware acceleration enabled in an earlier build and just forgot it was there. Removed that flag from my .conf file and everything is back to normal.
Offline