this post was submitted on 27 May 2025
17 points (94.7% liked)

Linux

11130 readers
245 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
 

Is this issue related to my ancient 15-year-old graphics card, my browser, or something else?

top 30 comments
sorted by: hot top controversial new old
[–] MRLimcon@lemmy.ml 3 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

One thing, always use hardware acceleration.

Does it get better if you set in about:config:

  • dom.ipc.processCount and dom.ipc.processCount.webIsolated to your number of threads on your cpu
  • gfx.webrender.all to true
  • fission.autostart to true

I think it would, in my suspicion, make a better use of your cpu (the threadpool would be more efficient in the processcount), using the new renderer (webrender) and possibly make it a little more secure with one thread per website (or something, i don't remember exactly) using fission.

Edit: An explanation on webrender

[–] KickassWomen@lemmy.world 1 points 2 weeks ago (1 children)

Making those changes didn't resolve the problem

[–] MRLimcon@lemmy.ml 1 points 2 weeks ago (1 children)

Can you test a newer version of firefox? I have 128 ESR on my work laptop and it's slow there too, it might be this.

[–] KickassWomen@lemmy.world 1 points 2 weeks ago (2 children)

This is apparently the latest version of Firefox ESR that's available in Debian's repository.

I used these commands to update Debian:

sudo apt update -y && sudo apt upgrade -y && sudo apt autoremove

Here's the output:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[–] MRLimcon@lemmy.ml 2 points 2 weeks ago (2 children)
[–] KickassWomen@lemmy.world 2 points 2 weeks ago (2 children)

I opened Firefox 134.0.2 (64-bit) that I installed via Flatpak—got the same slow pop-up issues.

[–] MRLimcon@lemmy.ml 2 points 2 weeks ago

Yeah, so it might be something else, IDK. Good luck!

[–] possiblylinux127@lemmy.zip 1 points 2 weeks ago (1 children)

What's the system resource usable look like?

[–] KickassWomen@lemmy.world 1 points 2 weeks ago (1 children)
[–] possiblylinux127@lemmy.zip 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

What's the CPU and what memory speed?

[–] KickassWomen@lemmy.world 1 points 1 week ago (1 children)

CPU: AMD Ryzen 7 5700X

As for my memory, I don't know the speed and I doubt that speed is the problem here because when I use Ungoogled Chromium, the javascript pop-up opens smoothly.

[–] possiblylinux127@lemmy.zip 2 points 1 week ago

That's a powerful CPU so I doubt that is the problem. I just wanted to get the obvious out of the way.

[–] KickassWomen@lemmy.world 2 points 2 weeks ago

Thanks but I want to stick with the ESR version. It's nice n' stable.

[–] possiblylinux127@lemmy.zip 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

https://flatpak.org/setup/Debian

Once you have Flatpak setup you can run sudo flatpak install firefox

Also, is there a reason you are using Debian? If that's what you want then that is fine but it isn't something people use for the new packages.

[–] KickassWomen@lemmy.world 1 points 2 weeks ago

Once you have Flatpak setup you can run sudo flatpak install firefox

I already have Flatpak installed and it has the same problem as Firefox ESR (which comes with Debian by default, if my memory serves me correctly)

Also, is there a reason you are using Debian? If that’s what you want then that is fine but it isn’t something people use for the new packages.

I have used Debian-based distros in the past like Mint and Ubuntu so I wanted to use Debian itself out of curiosity.

[–] GolfNovemberUniform@infosec.pub 2 points 2 weeks ago

It's most likely the CPU or less likely a browser bug.

[–] infeeeee@lemm.ee 2 points 2 weeks ago (1 children)

Just my troubleshooting tips:

Can you run a benchmark, maybe this one, so we can see it it's really a general thing not just something on that website? Also we can compare it to other computers, or you can see if changing a setting helps at all.

Can you see something strange in about:processes? Shift+Esc is its keyboard shortcut.

Can you try it in other browsers? Something Chrome like (Chromium, Brave, Vivaldi). Does this happen there as well?

[–] KickassWomen@lemmy.world 1 points 2 weeks ago (1 children)

Can you run a benchmark, maybe this one

Can you see something strange in about:processes?

I can't find anything suspicious but here's a snippet of it:

Can you try it in other browsers?

I used Ungoogled Chromium and it opens the pop-ups smoothly (so Firefox is causing the problem):

Clip

[–] infeeeee@lemm.ee 1 points 2 weeks ago (1 children)

Why the benchmark is at 90fps? What happens if you lower your monitor refresh rate to 60?

[–] KickassWomen@lemmy.world 1 points 2 weeks ago (1 children)

Lowered my monitor's refresh rate to 60 Hz and it didn't resolve the issue

[–] infeeeee@lemm.ee 1 points 2 weeks ago (1 children)

Also lower it in the DE settings. Are you on wayland?

[–] KickassWomen@lemmy.world 1 points 2 weeks ago

I changed it via Debian's Settings app.

I'm using X11 and Gnome.

[–] Max_P@lemmy.max-p.me 1 points 2 weeks ago (1 children)

What's the rest of the hardware? Tried disabling hardware acceleration and see if it makes a difference?

[–] KickassWomen@lemmy.world 1 points 2 weeks ago (1 children)

I disabled recommended performance settings and hardware acceleration in Firefox and I'm still experiencing this issue:

[–] Max_P@lemmy.max-p.me 5 points 2 weeks ago

Then it's not the GPU, as it doesn't appear to be using it in the first place.

[–] possiblylinux127@lemmy.zip 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Why are you using the ESR version?

I would either add the Mozilla repo or install the Flatpak

Edit: I saw your other comments

What desktop are you on?

[–] KickassWomen@lemmy.world 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

I have Flatpak Firefox and it's giving me the same issue as Firefox ESR.

I'm using Firefox ESR because Flatpak Firefox started freezing after a couple of updates and ESR is super stable.

As for my desktop: Gnome - X11

[–] possiblylinux127@lemmy.zip 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Have you tried switching to Wayland?

Log out and select the Wayland

[–] KickassWomen@lemmy.world 1 points 1 week ago (1 children)

I can't find that option in my login screen's gear icon menu. I think that the reason why I can't use Wayland is because I have a Radeon HD5450 graphics card that is 15 years old.

[–] possiblylinux127@lemmy.zip 2 points 1 week ago* (last edited 1 week ago)

Wayland doesn't care much about underlying hardware as that's abstracted away by the kernel level stuff.

Are you using GDM?

Edit: https://wiki.debian.org/Wayland#GNOME_.28supported_since_3.20.2B-.29

It looks like Wayland is the default