Open Bug 1956269 Opened 25 days ago Updated 24 days ago

Visual corruption with RTX 5000 series graphics cards with aniso + NVidia driver

Categories

(Core :: Graphics: WebRender, defect)

Firefox 136
x86_64
Windows 11
defect

Tracking

()

UNCONFIRMED

People

(Reporter: Tobias.Marty, Unassigned)

Details

Attachments

(1 file, 1 obsolete file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:136.0) Gecko/20100101 Firefox/136.0

Steps to reproduce:

Used Firefox with an RTX 5070 Ti and current drivers installed (572.83).

Actual results:

Numerous sites show visual corruption of different kinds, e.g. black lines, flickering lines...

Example screenshot from the following site attached: https://www.forum-3dcenter.org/vbulletin/newthread.php?do=newthread&f=43

Expected results:

Content gets rendered correctly.

There are many known bugs with visual corruption with RTX 5000 series graphics cards. However I didn't notice any problems with Chromium based web browsers.

I just noticed my screenshot didn't capture the errors. I have attached another screenshot.

Attached image visual bugs.png
Attachment #9474394 - Attachment is obsolete: true

I just noticed my screenshot didn't capture the errors. I have attached another screenshot.

Component: Untriaged → Graphics
OS: Unspecified → Windows 11
Product: Firefox → Core
Hardware: Unspecified → x86_64

So this if probably invalid/wontfix: It is caused when anisotropic filtering is forced globally in the nVidia driver. Shows corruption with RTX 5000 with WebRender, never did with older Geforce generations for me.

I'll leave that assessment to others :-)

Severity: -- → S4
Component: Graphics → Graphics: WebRender
Flags: needinfo?(gwatson)
Summary: Visual corruption with RTX 5000 series graphics cards → Visual corruption with RTX 5000 series graphics cards with aniso + NVidia driver

I think we've had a similar report previously - the aniso filtering is not compatible with the way we create texture atlases, which causes the artifacts. Unfortunately there's nothing we can do WR-side to prevent this (at least, not without very significant performance implications). Perhaps there is a way we could detect that aniso is being forced by the driver and warn users, or something like that.

Flags: needinfo?(gwatson)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: