Bug 2395768 - backdrop-filter: blur is laggy when GPU acceleration isn't available
Summary: backdrop-filter: blur is laggy when GPU acceleration isn't available
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 42
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-16 13:15 UTC by Samuel
Modified: 2026-06-09 11:16 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-06-09 11:16:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
HTML file that shows the problem (463 bytes, text/html)
2025-09-16 13:15 UTC, Samuel
no flags Details

Description Samuel 2025-09-16 13:15:29 UTC
Using backdrop-filter: blur in Firefox when no GPU acceleration is available makes things extremely laggy. One common case where this happens is when running Firefox in a remote desktop session. Backdrop-filter blur works well without GPU acceleration on Chromium 140.

Issue seen on both Firefox ESR 128 on Red Hat Enterprise Linux 9 and in Firefox 142 on Fedora 42. These are the packaged Firefox versions installed via DNF.

Reproducible: Always

Steps to Reproduce:
1. Open Firefox in a remote desktop session without GPU acceleration.
2. Open the attached HTML file.
3. Scroll to see the problem.
Actual Results:
Scrolling on the website is very, very slow.

Expected Results:
The blur property should work well, even on CPU fallback.

By disabling backdrop-filter in the web inspector, you can see that things start working normally again.

Additional Information:
Also reported to Firefox:

https://bugzilla.mozilla.org/show_bug.cgi?id=1988728

I cannot reproduce the issue on Fedora 42 with the nightly build of Firefox downloaded directly from Mozilla. Could this be an issue with Red Hat's Firefox builds?

Comment 1 Samuel 2025-09-16 13:15:57 UTC
Created attachment 2106787 [details]
HTML file that shows the problem

Comment 2 Fedora Release Engineering 2026-05-06 14:07:02 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Aoife Moloney 2026-06-09 11:16:17 UTC
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27.

Fedora Linux 42 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.