@tartanpion re: why it failed:
In one case I compiled with v4l2 without disabling vaapi, and in the other case I think I tried to compile chromium from archlinux (non-ALARM)
Some of my observations:
The V4L2 decoder usually crashes on twitch and youtube, and chromium immediately replaces it with FFmpegVideoDecoder.
On my OPi5+, when I run ozone-backend=x11 (which doesn’t use explicit-sync from the mentioned commit), then the video stutters every few seconds.
I personally avoid the crashes by using the Vulkan backend. Unfortunately vulkan-panfrost is not bug-free. Some websites have graphical glitches and V4L2 videos often end up with major glitches.
On my Opi5+ with “ozone-platform=wayland” and using enhanced-h264ify to limit to h264, the video stream smoothly. Currently on RK3588 the v4l2request only support h264 format. At times can stream youtube for 15 minutes or more but does crashes randomly.
Same experience launching Chromium with X11, video stutters.
That commit adds a fallback for explicit sync. It is no longer relevant today, since chromium nowadays does explicit sync using the drm-syncobj wayland protocol. On rk3588, this still crashes, albeit less often.
I compiled chromium with WaylandBufferManagerHost::SupportsAcquireFence() changed to always return false. Seems to work. It hasn’t crashed yet.
What puzzles me is that the commit message says that explicit sync is required for vulkan to work, but vulkan somehow still works?
I think vulkan requires X11 to work on chromium. I recently switched to wayland and if i activate vulkan, i lose all hw acceleration. Under X11 that wasn’t the case.