Chromium seems to have lost support for graphics acceleration on Wayland

[luc4]

Hello!
I just noticed that I’m unable to run Chromium with graphics acceleration on Wayland.

I used to run Chromium like this:

chromium --enable-features=UseOzonePlatform --ozone-platform=wayland

and it used to work properly. Now in about://gpu I see:

Graphics Feature Status
* Canvas: Software only. Hardware acceleration disabled
* Canvas out-of-process rasterization: Disabled
* Direct Rendering Display Compositor: Disabled
* Compositing: Software only. Hardware acceleration disabled
* Multiple Raster Threads: Disabled
* OpenGL: Disabled
* Rasterization: Software only. Hardware acceleration disabled
* Raw Draw: Disabled
* Video Decode: Software only. Hardware acceleration disabled
* Video Encode: Software only. Hardware acceleration disabled
* Vulkan: Disabled
* WebGL: Disabled
* WebGL2: Disabled
* WebGPU: Disabled

This is what I find at the bottom:

* [292607:292607:0402/131154.980821:WARNING:sandbox_linux.cc(393)] : InitializeSandbox() called with multiple threads in process gpu-process.
* [292607:292607:0402/131155.109215:ERROR:gbm_pixmap_wayland.cc(75)] : Cannot create bo with format= RGBA_8888 and usage=SCANOUT
* [292607:292607:0402/131155.109309:ERROR:gbm_pixmap_wayland.cc(75)] : Cannot create bo with format= RGBA_8888 and usage=GPU_READ
* [292607:292607:0402/131155.109367:ERROR:shared_image_factory.cc(661)] : CreateSharedImage: could not create backing.
* [292607:292607:0402/131155.109425:ERROR:shared_image_factory.cc(516)] : DestroySharedImage: Could not find shared image mailbox
* GpuProcessHost: The GPU process exited with code 8704.
* [292692:292692:0402/131155.225869:WARNING:sandbox_linux.cc(393)] : InitializeSandbox() called with multiple threads in process gpu-process.
* [292692:292692:0402/131155.270821:ERROR:gbm_pixmap_wayland.cc(75)] : Cannot create bo with format= RGBA_8888 and usage=SCANOUT
* [292692:292692:0402/131155.270966:ERROR:gbm_pixmap_wayland.cc(75)] : Cannot create bo with format= RGBA_8888 and usage=GPU_READ
* [292692:292692:0402/131155.271055:ERROR:shared_image_factory.cc(661)] : CreateSharedImage: could not create backing.
* [292692:292692:0402/131155.271114:ERROR:shared_image_factory.cc(516)] : DestroySharedImage: Could not find shared image mailbox
* GpuProcessHost: The GPU process exited with code 8704.
* [292733:292733:0402/131155.381275:WARNING:sandbox_linux.cc(393)] : InitializeSandbox() called with multiple threads in process gpu-process.
* [292733:292733:0402/131155.467999:ERROR:gbm_pixmap_wayland.cc(75)] : Cannot create bo with format= RGBA_8888 and usage=SCANOUT
* [292733:292733:0402/131155.468103:ERROR:gbm_pixmap_wayland.cc(75)] : Cannot create bo with format= RGBA_8888 and usage=GPU_READ
* [292733:292733:0402/131155.468167:ERROR:shared_image_factory.cc(661)] : CreateSharedImage: could not create backing.
* [292733:292733:0402/131155.468277:ERROR:shared_image_factory.cc(516)] : DestroySharedImage: Could not find shared image mailbox
* [292733:292733:0402/131155.468414:ERROR:gpu_service_impl.cc(980)] : Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
* GpuProcessHost: The GPU process exited with code 8704.
* GpuProcessHost: The GPU process crashed!
* GpuProcessHost: The GPU process crashed!
* GpuProcessHost: The GPU process crashed!
* [292831:292831:0402/131157.137740:ERROR:gpu_init.cc(525)] : Passthrough is not supported, GL is disabled, ANGLE is

The same happens in Google Chrome and Brave. Using XWayland fixes the problem. Anyone else who experiences the same? I think this started recently. Maybe a new bug in Chromium?
Thanks!

[cscs]

I would be surprised if you didnt need more flags than that.
In any case please see this section and the one after at the arch wiki
Chromium - ArchWiki
Chromium - ArchWiki

We dont know what your system/gpu/etc is. So maybe its worth mentioning this too
https://forum.manjaro.org/t/behind-the-scene-manjaro-community-mesa-nonfree-codecs/135012

[luc4]

Actually yes, I think graphic acceleration worked with those flags alone, for some months at least. And it still does without any param with XWayland it seems. I completely reset the params and just starting Chromium without params shows graphics acceleration enabled (but XWayland).

This is more or less what the doc suggests it seems:

chromium --enable-features=UseOzonePlatform --ozone-platform=wayland --ignore-gpu-blocklist --enable-gpu-rasterization --enable-zero-copy --disable-gpu-driver-bug-workarounds --enable-features=VaapiVideoDecoder

at the moment, video acceleration would be a plus, so let’s ignore vaapi unless it is mandatory. I tried those params in many combinations but I still get no graphics acceleration when Chromium is a Wayland native client.

System is:

6.1.21-1-MANJARO #1 SMP PREEMPT_DYNAMIC Wed Mar 22 21:14:13 UTC 2023 x86_64 GNU/Linux
KDE Plasma: 5.27.3
Qt version: 5.15.8
CPU: 8 × Intel® Xeon® CPU E3-1505M v6 @ 3.00GHz
GPU: Intel® HD Graphics P630

The system also includes a nVidia GPU, but I never use it.

The most interesting point is if someone else noticed this problem recently. Anyone else with a similar GPU that has no problems in the same context?

Thanks for your help.

[koshikas]

this remain the best resource for manjaro on the topic (even chronologically);

[HowTo] Enable Hardware Video Acceleration / Video Decode In Google Chrome, Brave, Vivaldi And Opera Browsers

Difficulty: ★★☆☆☆ Requirements: Google Chrome >=88 Brave >= 1.19 Vivaldi >=3.6 Opera >=74 For Chromium and Firefox, see their corresponding Arch Wiki articles: Chromium: Hardware video acceleration Firefox: Hardware video acceleration Note: This doesn’t work on Wayland. You can use VA-API on XWayland, using the --use-gl=egl command line flag (untested). 1. Enable the following web browser flags: Warning: Disabling the rendering blacklist may cause unst…

[luc4]

Appartenly, the problem is solved. No idea how but, completely by accident, I found that graphics acceleration in Brave was restored. I checked, and also Chromium is ok.

I’m sorry but I am unable to describe how I fixed it, because everything I did seemed to make no difference. I suspect a simple reboot fixed it. Running Chromium (or Brave), like this:

chromium --enable-features=UseOzonePlatform --ozone-platform=wayland

results in this configuration, as I said my original message:

* Canvas: Hardware accelerated
* Canvas out-of-process rasterization: Disabled
* Direct Rendering Display Compositor: Disabled
* Compositing: Hardware accelerated
* Multiple Raster Threads: Enabled
* OpenGL: Enabled
* Rasterization: Hardware accelerated
* Raw Draw: Disabled
* Video Decode: Hardware accelerated
* Video Encode: Software only. Hardware acceleration disabled
* Vulkan: Disabled
* WebGL: Hardware accelerated
* WebGL2: Hardware accelerated
* WebGPU: Disabled

the difference in the performance is clearly noticeable.

Apparently, decoding is reported as hardware accelerated. However, I checked and I cannot confirm any acceleration is in place. I opened a simple mp4 with an h264 stream, and Intel top does not report any activity for the video decoder. I also tried the “–enable-features=VaapiVideoDecoder” parameter, but nothing changed. No idea why it thinks decoding is accelerated.

Thanks for your help!