hey i recently find a issue that if play a video from youtube in firefox and chromium/brave i find firefox using more cpu then chromium base browser why this is happening can anyone explain btw my firefox was installed from dnf but brave was with flatpak
You probably aren’t getting hardware acceleration in firefox but are in brave.
I have tried with flatpak version of the firefox but same as it was in from .rpm
I will loook into
What’s your hardware? Share the output of
vainfo -a and
I experienced the same thing on an Intel processor with internal graphics with flatpaked firefox beta. It’s much improved since I installed intel-media-driver and generally just followed the guide linked by @ozeszty. In the flatpaked version you might have to allow firefox to use hardware acceleration through flatseal or commandline
I find it is same for both flatpak and .rpm i find even ungoogled chromium have lower cpu usage thn firefox almost half.
Check which codecs and what resolutions are being used (e.g. YT stats for nerds) and what can be hardware accelerated (with
Even without HW acceleration difference, cpu usage can differ substantially between h264 (avc1) and e.g. vp9 or av1.
anyway…I’m getting trouble firefox, recently unstable status for me! Take care!!!
$ vainfo bash: vainfo: command not found...
i am on wayland so it should work out of the box.
still i am installing ffmpeg, libva and libva-utils this three packages
installing 3 packages does not solve anything
$ vainfo libva info: VA-API version 1.15.0 libva info: Trying to open /usr/lib64/dri/r600_drv_video.so libva info: Found init function __vaDriverInit_1_15 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.15 (libva 2.15.0) vainfo: Driver version: Mesa Gallium driver 22.2.0 for AMD RS780 (DRM 2.50.0 / 5.19.16-301.fc37.x86_64, LLVM 15.0.0) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc
This is UVD 2.0 GPU supporting MPEG4 AVC and VC1 decode: https://www.x.org/wiki/RadeonFeature/#radeonuvdunifiedvideodecoderhardware
Those are missing in
vainfo output because you’re using F37 in witch some VA-API drivers (including AMD) were dropped because of licensing issues: https://email@example.com/thread/PYUYUCM3RGTTN4Q3QZIB4VUQFI77GE5X/
Here’s review request for providing dropped drivers in RPMFusion: https://bugzilla.rpmfusion.org/show_bug.cgi?id=6426
Flatpak has it’s own mesa with those drivers still included (at least for now), hence flatpacked apps can use all hardware decoding capabilities and the difference in CPU usage. With drivers in RPMFusion the difference will once again disappear.
But then why flatpak one also same as .rpm one is there a reason. As i have checked with brave and ungoogled chromium that both works without a issue. I find it particularly in only firefox though.
They are not the same. Don’t ever claim that.
The version may be the same but the packages are different.
The rpm only installs what fedora allows and provides.
The flatpak installs additional apps, libraries, etc to enable running without the same restrictions as fedora has.
Brave and chromium come from a 3rd party repo so they are not restricted the same as the fedora provided firefox from rpm. Same for the flatpak in that it also is not under the same restrictions as the rpm version.
Fedora does not distribute any license, copyright, or patent encumbered software. 3rd party developers and packaging sites are not under the same limitations.
this issues still there does not solved yet
$ glxinfo | grep "profile version" Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES profile version: 3.0 OpenGL core profile version string: 3.3 (Core Profile) Mesa 22.3.6 OpenGL ES profile version string: OpenGL ES 3.0 Mesa 22.3.6
$ rpm -qa | grep mesa mesa-filesystem-22.3.6-1.fc37.x86_64 mesa-libglapi-22.3.6-1.fc37.x86_64 mesa-dri-drivers-22.3.6-1.fc37.x86_64 mesa-libgbm-22.3.6-1.fc37.x86_64 mesa-libEGL-22.3.6-1.fc37.x86_64 mesa-libGL-22.3.6-1.fc37.x86_64 mesa-libxatracker-22.3.6-1.fc37.x86_64 mesa-vulkan-drivers-22.3.6-1.fc37.x86_64 mesa-va-drivers-freeworld-22.3.6-1.fc37.x86_64 mesa-vdpau-drivers-freeworld-22.3.6-1.fc37.x86_64