@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.
Hopefully this can be default chromium build on alarm repo too.
Edit: 2025-06-05
Manjaro-opi5plus-xfce-6.15.1-1 (labwc-wayland-session) chromium-137.0.7151.55-2 streaming 1080/60 videos with hardly any drop frames using “V4L2VideoDecoder”. Good.
So far chromium-137.0.7151.55-2 is stable on “–ozone-platform=wayland”.
That sounds great. This was only possible on x11. You got me interested now i will just remove the flatpak version and install this.
Is there any flag i should enter to get the v4l2 video decoder working?
By the way, the last update was on january. Arch Arm seems like they have given up on chromium and will no longer update it. Can we (manjaro arm) have a different repository for our own chromium then? Would that be possible?
Flatpak version was just updated to 137. I tried to open a youtube video (1080p 60hz) and although it is still watchable, it still drops a bunch of frames.
Ok so people can build chromium for their own manjaro arm setups and post their installation packages, that is fine but, if they can do it, arch arm itself should be able to do it. So why don’t they? I just checked and it is still version 131. I am fine with using the flatpak version for the moment but why is chromium being neglected like this? It is not Google Chrome, it is the open source chromium. It should be available.
Arch arm webpage and forum is struggling lately, all the more fire to the suspicion that arch arm is dying. If you haven’t received the confirmation e-mail by now (it was instant for me), you won’t receive it any time soon. I seriously think that, just maybe, Manjaro ARM should start considering a backup strategy in the case that arch arm gives up the ghost. Gentoo maybe? Or Alpine?