Package Details: chromium-framerate-fix 105.0.5195.102-1

Git Clone URL: https://aur.archlinux.org/chromium-framerate-fix.git (read-only, click to copy)
Package Base: chromium-framerate-fix
Description: Chromium with a patch to set custom framerate. Fixes Chromium choppiness with EGL and Desktop backends
Upstream URL: https://www.chromium.org/Home
Keywords: chromium
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: Kerriganx
Maintainer: Kerriganx
Last Packager: Kerriganx
Votes: 2
Popularity: 0.102802
First Submitted: 2022-01-23 11:43 (UTC)
Last Updated: 2022-09-03 11:44 (UTC)

Dependencies (50)

Required by (110)

Sources (8)

Pinned Comments

Kerriganx commented on 2022-01-23 11:46 (UTC) (edited on 2022-06-21 12:58 (UTC) by Kerriganx)

This package will be useful for people who have high frame rate monitor and want to use VAAPI for hardware acceleration.

If you start chromium with --use-gl=desktop (Nvidia) or --use-gl=egl (AMD) flag (required in order for VAAPI to work) the browser framerate will locks to 60 Hz. This package fixes Chromium choppiness by changing hardcoded fps from 60 to 165 (you can change in PKGBUILD). I hope someone can fix this issue in a proper way instead of such a dirty hack. But for now those who don't want to wait can use this package as temporary solution.

--disable-features=UseChromeOSDirectVideoDecoder required for Chromium 98+

In PKBUILD under prepare() there is option to set custom framerate. The default is 165, but you can change it to 144 or whatever.

How long does it take to build? A really long time.

Latest Comments

joshtau commented on 2022-10-17 12:20 (UTC)

Seems to throw a 404 for the github link. Seems to be here, though for Chromium 108: https://github.com/stha09/chromium-patches/releases/tag/chromium-108-patchset-2

https://github.com/stha09/chromium-patches/releases/download/chromium-108-patchset-2/chromium-108-patchset-2.tar.xz

Kerriganx commented on 2022-07-23 00:13 (UTC) (edited on 2022-07-23 00:32 (UTC) by Kerriganx)

Someone just filed a deletion request for this package: "Please file a bug report with your proposed fix instead of creating a duplicate package."

I can explain why this package is useful and don't need deletion. The proposed fix is not a proper solution. It's a very dirty hack by changing hardcoded fps in sorce code. This patch won't be accepted into the main package. In fact, this is a workaround for a bug not in Chromium, but in Mesa and Nvidia drivers. Until this (https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15381) will be merged this package is useful. Also we don't know when it will be fixed in Nvidia. Until this happens, we don't need to remove this package.

Kerriganx commented on 2022-01-23 11:46 (UTC) (edited on 2022-06-21 12:58 (UTC) by Kerriganx)

This package will be useful for people who have high frame rate monitor and want to use VAAPI for hardware acceleration.

If you start chromium with --use-gl=desktop (Nvidia) or --use-gl=egl (AMD) flag (required in order for VAAPI to work) the browser framerate will locks to 60 Hz. This package fixes Chromium choppiness by changing hardcoded fps from 60 to 165 (you can change in PKGBUILD). I hope someone can fix this issue in a proper way instead of such a dirty hack. But for now those who don't want to wait can use this package as temporary solution.

--disable-features=UseChromeOSDirectVideoDecoder required for Chromium 98+

In PKBUILD under prepare() there is option to set custom framerate. The default is 165, but you can change it to 144 or whatever.

How long does it take to build? A really long time.