You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 3, 2022. It is now read-only.
The flashing "Information" and "Options" icons in the top right take up 10-30% CPU usage when the tab is focused, occasionally setting off my laptop's fans. (Both clicking them and switching to another tab relieve it.) Could you switch to a less intensive way of marking them?
I'm using Firefox 78.3.0 ESR on Debian. The usage doesn't show up in about:performance, but it does show up as a process called "GPU Process" in gnome-system-monitor and "firefox-esr [...] gpu" in htop.
Haven't reproduced it myself with MacOS/Chrome. Just wanted to submit their report here.
The text was updated successfully, but these errors were encountered:
ibis85
changed the title
High GPU usage from blinking navbar icons
High CPU usage from blinking navbar icons
Oct 24, 2020
Those are native CSS animations and are supposed to be completely
unnoticeable in performance. It's either an issue with your browser or the
GPU drivers on your laptop.
On Sat, 24 Oct 2020 at 10:24, ibis85 ***@***.***> wrote:
A user reported the following:
The flashing "Information" and "Options" icons in the top right take up
10-30% CPU usage when the tab is focused, occasionally setting off my
laptop's fans. (Both clicking them and switching to another tab relieve
it.) Could you switch to a less intensive way of marking them?
I'm using Firefox 78.3.0 ESR on Debian. The usage doesn't show up in
about:performance, but it does show up as a process called "GPU Process" in
gnome-system-monitor and "firefox-esr [...] gpu" in htop.
Haven't reproduced it myself with MacOS/Chrome. Just wanted to submit
their report here.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1248>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB347MC63CTBCGM2UZWRJ43SMJ6JHANCNFSM4S5MWQOA>
.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A user reported the following:
Haven't reproduced it myself with MacOS/Chrome. Just wanted to submit their report here.
The text was updated successfully, but these errors were encountered: