Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

Firefox lags after locking OS

  • 2 réponses
  • 0 a ce problème
  • 64 vues
  • Dernière réponse par 1majom
  • Archivé

1majom
1majom

If I lock my machine for more than a few minutes and then log on again, it's always the same. I unlock my system and feel some kind of slowness in Firefox. When I switch from the currently open tab in Firefox, the new tab is highlighted in the tab bar, but the content part of the window is frozen. If I quickly open htop, I can see that the main Firefox process is suddenly using about 130% of my CPU. The only solution I have found is to quickly open htop after unlocking the system, send a SIGKILL to the main Firefox process and reopen it. This way the freezing, slowing problem is nowhere to be seen.

I am running Debian 12 with Firefox 115.4.0esr (64-bit). I have more than enough RAM and CPU.

If I lock my machine for more than a few minutes and then log on again, it's always the same. I unlock my system and feel some kind of slowness in Firefox. When I switch from the currently open tab in Firefox, the new tab is highlighted in the tab bar, but the content part of the window is frozen. If I quickly open htop, I can see that the main Firefox process is suddenly using about 130% of my CPU. The only solution I have found is to quickly open htop after unlocking the system, send a SIGKILL to the main Firefox process and reopen it. This way the freezing, slowing problem is nowhere to be seen. I am running Debian 12 with Firefox 115.4.0esr (64-bit). I have more than enough RAM and CPU.

Toutes les réponses (2)

zeroknight
zeroknight

1majom said
the content part of the window is frozen.

If the content updates when you switch to a different window (eg Alt+Tab), you may be able to rescue it by going to about:support and clicking the button next to "Device Reset" (may appear as "gpu-device-reset").

You might be able to avoid it by disabling hardware acceleration and/or running in native Wayland by setting the environment variable MOZ_ENABLE_WAYLAND=1.

1majom
1majom Auteur de la question

zeroknight said
If the content updates when you switch to a different window (eg Alt+Tab), ...

Sadly switching to an other window never helped. But I will try disabling hardware acceleration and will reply.