Summary: | www-client/google-chrome: Accelerated compositing nonfunctional unless seccomp sandbox is disabled | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrew Athalye <andrewathalye> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andrew Athalye
2022-01-24 03:16:43 UTC
Maybe https://crbug.com/1256824 ? The reporter claims that it works with current google-chrome-beta (M98). I was able to reproduce it with Chromium from the appspot download site (basically the trunk build), however I'll check Google Chrome Beta to see if maybe they have some build flags enabled that make it work there. (In reply to Andrew Athalye from comment #2) > I was able to reproduce it with Chromium from the appspot download site > (basically the trunk build), however I'll check Google Chrome Beta to see if > maybe they have some build flags enabled that make it work there. After a very brief check using www-client/google-chrome-beta, I was able to reproduce the same behaviour where Hardware compositing is only functional if the bpf sandbox is disabled. When I have some free time I'll look into the chromium source to see if a modification to the sandbox to exempt the syscall for loading the NVIDIA shared object files would work. Just one final comment: in the Beta build I tried, Canvas was listed as hardware accelerated under Wayland in chrome://gpu, but Compositing was still software-only. This may be the change that the crbug was alluding to, as in the Chromium trunk build this was also the case. No hardware acceleration at all works by default in the stable build. Have the same on an AMDGPU with google-chrome-98.0.4758.80 on X11. Works with google-chrome-beta-99.0.4844.17. Interestingly starts on a machine with nvidia-drivers-510.47.03. But freezes X11 then which has always been the case on that particular machine/ setup also with previous versions. Forget about my comment #5, context totally wrong. |