Closed Bug 1601204 Opened 5 years ago Closed 4 years ago

There are Visual Glitches when resizing the browser window with WebRender on Laptops with Nvidia GPU

Categories

(Core :: Graphics, defect, P5)

Desktop
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox71 --- disabled
firefox72 --- affected
firefox73 --- affected

People

(Reporter: rdoghi, Unassigned)

References

Details

Attachments

(3 files)

Attached video 2019-12-04_11h31_14.mp4

[Affected versions]:
Nightly 73.0a1

[Affected platforms]:
Platforms: Windows 10

[Prerequisites]:
Ensure that in about:support at Graphics section “Compositing” has the “WebRender” attribute, if not set gfx.webrender.all to true.
Laptop with NVIDIA GeForce GTX 1650

Steps :

  1. Open the Firefox Browser.
  2. Drag the Corner of the Browser window in order to resize it multiple times. (Faster this is done the more noticable the issue is).

Expected Results :
Browser is resized properly and no visual glitches are displayed.

Actual Results :
Visual Glitches are displayed when resizing the window. Please see the attached video.

Summary: There are Visual Glitchers when resizing the browser window with WebRender on Laptops with Nvidia GPU → There are Visual Glitches when resizing the browser window with WebRender on Laptops with Nvidia GPU
Attached file aboutSupport.txt

Also added the aboutSupport file

Blocks: wr-72
Priority: -- → P2

Rares, do you have another Nvidia Laptop where you can try to reproduce this bug?

Flags: needinfo?(rares.doghi)

Hi, I have retested this issue on a different Dell Laptop, with Nvidia Geforece GTX 1050 and the issue still occurs, now I do have a few details that might help in reproducing this issue, I'm not sure how relevant they are but I really hope they help so we can get to the bottom of this issue.

First things first, Both of these Dell Laptops already have the Intel UHD Graphics 630 as their main GPU, I changed this manually by going to:

Nvidia Control Panel > Manage 3D Settings > Global Settings > Preferred graphics processor > High-performance Nvidia processors (selected from the drop down)
Nvidia Control Panel > Manage 3D Settings > Program Settings > Select a program to customize > (firefox nightly from the drop down)

These two settings will force Firefox to have the Nvidia GPU as their #1 Active GPU that activates WebRender.

I will attach the About:Support file from the second Dell Laptop.

Flags: needinfo?(rares.doghi) → needinfo?(jbonisteel)

Hey Alexis - can you try retesting this on an Nvidia laptop in TO and if it doesn't happen, can we document if there are any differences between the card/driver/etc?

Flags: needinfo?(jbonisteel) → needinfo?(a.beingessner)

@Rares Doghi: Does this have a regression range?
@sotaro: Is this related to bug 1579732 and bug 1572096? (CompositorWindow/DoubleBuffering/DXGI_SWAP_EFFECT_FLIP_SEQUENTIAL)

Rares, If you don't force the Nvidia GPU to be used by Firefox and you force WebRender on (i.e. WebRender on Intel) do you see the same problem on those laptops?

Flags: needinfo?(rares.doghi)

I have the same issue in Firefox 71 with Intel Iris Graphics.

(In reply to unahombre1 from comment #8)

I have the same issue in Firefox 71 with Intel Iris Graphics.

It might be similar bug with my issue here:

https://bugzilla.mozilla.org/show_bug.cgi?id=1600496

Hi Jeff, There is no regression range for this issue , I don't think Webrender was supported on laptops in older versions of Firefox but I did see this issue occur in Release Beta and Nightly, also if I don't Force Nvidia from the 3D panel and the Intel GPU is the one that activates WebRender this issue does not occur.

Flags: needinfo?(rares.doghi)

We have been trying to reproduce this on additional hardware today and still no luck.

Rares, can you confirm that you don't see this issue in Nightly with WebRender turned off?

Flags: needinfo?(rares.doghi)

Hi Jeff, I have retested this issue in our latest Nightly build 73.0a1 (2019-12-15) and the issue does not reproduce anymore with or without WebRender ON, it only occurs in Beta now.

Flags: needinfo?(rares.doghi)

I wonder if it might be related to WR native compositor usage. In this case, Bug 1604088 might revive the problem to nightly.

(In reply to Rares Doghi from comment #13)

Hi Jeff, I have retested this issue in our latest Nightly build 73.0a1 (2019-12-15) and the issue does not reproduce anymore with or without WebRender ON, it only occurs in Beta now.

Do you see it on Beta with WebRender off?

Flags: needinfo?(rares.doghi)

Yes I was able to reproduce it with WebRender off as well. In Beta 72.0b7.

Flags: needinfo?(rares.doghi)

Hi Jeff, after retesting this issue in our latest nightly build 73.0a1 (2020-01-03) We noticed that this issue reoccurs in Nightly as well.

Flags: needinfo?(jmuizelaar)

Rares, can you confirm if it still happens with WebRender off as well?

Flags: needinfo?(rares.doghi)
Blocks: wr-wild
No longer blocks: wr-72
Flags: needinfo?(jmuizelaar)

Yes its a little less noticeable with WebRender off but it still happens in 73.0a1 (2020-01-05).

Flags: needinfo?(rares.doghi)
Blocks: not-wr
No longer blocks: wr-wild
Component: Graphics: WebRender → Graphics
Priority: P2 → P5
Flags: needinfo?(a.beingessner)
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: