Package Details: firefox-vaapi 133.0-1

Git Clone URL: https://aur.archlinux.org/firefox-vaapi.git (read-only, click to copy)
Package Base: firefox-vaapi
Description: Fast, Private & Safe Web Browser (with VA-API patches)
Upstream URL: https://www.mozilla.org/firefox/
Keywords: firefox libva va-api vaapi video
Licenses: MPL-2.0
Conflicts: firefox
Provides: firefox
Submitter: ewout
Maintainer: dcelasun
Last Packager: dcelasun
Votes: 11
Popularity: 0.038505
First Submitted: 2023-02-24 13:48 (UTC)
Last Updated: 2024-12-01 12:05 (UTC)

Required by (171)

Sources (7)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

dcelasun commented on 2024-06-16 15:51 (UTC)

I never could build it with 32GB, only saw success with 64GB+ systems.

deemon commented on 2024-06-16 15:24 (UTC) (edited on 2024-06-16 15:27 (UTC) by deemon)

fails to build in 32GB system... tried twice. second time closed everything else.

juuni 16 15:57:18 Zen kernel: Out of memory: Killed process 822286 (ld.lld) total-vm:41427260kB, anon-rss:23011120kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:78396kB oom_score_adj:200
juuni 16 18:20:45 Zen kernel: Out of memory: Killed process 895458 (ld.lld) total-vm:44122236kB, anon-rss:24177960kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:81168kB oom_score_adj:200

any hints, how to limit the memory gobbling, so it doesn't fill entire memory, so it doesn't get automatically killed?

dcelasun commented on 2024-05-10 14:52 (UTC)

@BryanLiang thanks, pushed a fix with that patch. Unfortunately, I can't include the patch on AUR as it exceeds AUR's max file size limit (~488KiB) so it'll have to be downloaded from Gitlab.

BryanLiang commented on 2024-05-10 14:39 (UTC) (edited on 2024-05-10 14:43 (UTC) by BryanLiang)

I built fail in clean chroot, here is the build log: https://pastebin.com/raw/ikYigyc5.

It seem that it needs a patch: https://gitlab.archlinux.org/archlinux/packaging/packages/firefox/-/commit/5577acf6c2a83d81ffa538885f1b6258ed32d7db

dcelasun commented on 2024-05-10 13:35 (UTC)

Adopted package and updated to 125.0.3. Wayland proxy patches have been dropped as they have been upstreamed, and PGO seems to work correctly once again.

dcelasun commented on 2024-03-11 11:05 (UTC)

wayland-proxy patches are no longer needed as of Firefox 123.

NRG commented on 2024-02-12 10:12 (UTC)

I get basically the same error. My knowledge here is very limited; but it seemingly has to do with mesa, starting somewhere at 23.3.3? See aur/mesa-git comments.

dcelasun commented on 2024-02-05 22:47 (UTC) (edited on 2024-02-05 22:47 (UTC) by dcelasun)

Under X11 with Nvidia (not sure if relevant) PGO build fails with:

started SP3 server on port 8000                                                                                                                                                                
DRI3 not available       
failed to load driver: zink
console.warn: services.settings: Ignoring preference override of remote settings server
console.warn: services.settings: Allow by setting MOZ_REMOTE_SETTINGS_DEVTOOLS=1 in the environment
ATTENTION: default value of option mesa_glthread overridden by environment.
MESA: error: CreateSwapchainKHR failed with VK_ERROR_OUT_OF_DEVICE_MEMORY
MESA: error: zink: could not create swapchain
ExceptionHandler::GenerateDump cloned child 13022
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error. 
Exiting due to channel error.        
Firefox exited with code 11 during profile initialization

It seems like VK_ERROR_OUT_OF_DEVICE_MEMORY is a red herring, there is plenty of VRAM available. Non-PGO build works fine.

unknown78 commented on 2024-01-27 23:42 (UTC)

Just an info -> i was only able to compile 122 in a full wayland session. X11 or a terminal werent able to run the requiered tests with and zink environment.

X11: zinkrun glxgears

DRI3 not available
failed to load driver: zink
Error: couldn't get an RGB, Double-buffered visual

gamescope with a terminal inside wasn't enough it broke once it should have started the test session with the compiled firefox

a tty (aka login shell / terminal) did complain it couldn't start the tests either

I got it compiled under plasma wayland but othere wayland based environments might work too. I also needed to close the spawned firefox window ...

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »