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

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër
E zgjidhur Arkivuar

Very slow web page scroll on second monitor

prorock

I have two monitors. When I move firefox window to the second montior - scrolling of web pages is very slow. Sometimes it freeze computer (I can not move the mouse cursor). I was checked other applications like MS Word, Chrome. This problem is only firefox problem.

This problem apears when the part of firefox window is showing on the second monitor (even 50 pixels)

I have two monitors. When I move firefox window to the second montior - scrolling of web pages is very slow. Sometimes it freeze computer (I can not move the mouse cursor). I was checked other applications like MS Word, Chrome. This problem is only firefox problem. This problem apears when the part of firefox window is showing on the second monitor (even 50 pixels)

Krejt Përgjigjet (4)

Zgjidhja e Zgjedhur

Hey, I had the same problem and I resolved it: 1.- In Firefox menu, display Tools/Options; 2.- Unselect the box "use hardware acceleration when available". It should work better now. Apparently the hardware acceleration makes problems only when the windows of Firefox is shown in a non primary monitor (don't know why). I guess you know but if you want to change your primary monitor you can do it from settings (right click on desktop and then properties). Good luck!

Excellent. It's working :) Thanks!!!. Exact path to this option: Tools -> Options -> Advanced -> General -> Browsing -> Use hardware acceleration when available.

I have 3 monitors, and had this problem on the two that weren't the primary. Turning off "use hardware acceleration" worked, *BUT* only after I restarted Firefox. Thanks to those who found this workaround!

Turning off hardware acceleration fixes the issue for me. However, this shows that there is a serious bug in the hardware acceleration implementation. And clearly, we are losing the advantage of HW acceleration until this is fixed.