Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

Font rendering issues with hardware acceleration enabled

  • 2 trả lời
  • 0 gặp vấn đề này
  • 1 lượt xem
  • Trả lời mới nhất được viết bởi mail1896

more options

Hello :) Since one of the 2022 Firefox updates, I am constantly experiencing font rendering issues when the hardware acceleration is enabled. It occurs after a while of browsing on all websites, regardless of font family. See the attached screenshots.

Windows 11 Pro (upgraded from 10 where the problem also occured), GeForce GTX 1070Ti, 2x 4k monitor.

I reinstalled nVidia drivers from scratch, cleared the Firefox data, even experimented a bit with Direct2D settings in about:config; disabling the extensions (ABP, Simple Tab Groups) does not help either. The problem disappears completely when the hardware acceleration is off, but obviously I would like to have it on (for Google Maps, Twitch, hi-res videos, etc.)

I've always loved Firefox and still do. How do I make it love me back? ((-;

Hello :) Since one of the 2022 Firefox updates, I am constantly experiencing font rendering issues when the hardware acceleration is enabled. It occurs after a while of browsing on all websites, regardless of font family. See the attached screenshots. Windows 11 Pro (upgraded from 10 where the problem also occured), GeForce GTX 1070Ti, 2x 4k monitor. I reinstalled nVidia drivers from scratch, cleared the Firefox data, even experimented a bit with Direct2D settings in about:config; disabling the extensions (ABP, Simple Tab Groups) does not help either. The problem disappears completely when the hardware acceleration is off, but obviously I would like to have it on (for Google Maps, Twitch, hi-res videos, etc.) I've always loved Firefox and still do. How do I make it love me back? ((-;
Đính kèm ảnh chụp màn hình

Giải pháp được chọn

The reason was a faulty video card, everything's been fine since the card was replaced (and it also had been fine with the integrated graphics). Thank you for the support anyway, long live Firefox!

Đọc câu trả lời này trong ngữ cảnh 👍 0

Tất cả các câu trả lời (2)

more options

You can use mozregression to find when it started.

more options

Giải pháp được chọn

The reason was a faulty video card, everything's been fine since the card was replaced (and it also had been fine with the integrated graphics). Thank you for the support anyway, long live Firefox!