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

Steps to reproduce:

Enabled SLI on my PC with two GTX 970s. I have 4 monitors attached to the master card and 1 monitor attached to the Intel IGP.

Actual results:

Firefox windows are entirely black when they are put on the monitor that is connected to the IGP.

Expected results:

Firefox should behave on this monitor as on all other monitors.

The priority flag is not set for this bug.
:jbonisteel, could you have a look please?

For more information, please visit auto_nag documentation.

We should see if we can reproduce something like this locally.

If you drag a window from the nvidia display to the intel display when does it go black? Is this a recent regression or has it been broken for a while? Can you post the graphics section of about:support?

(In reply to Jeff Muizelaar [:jrmuizel] from comment #3)

If you drag a window from the nvidia display to the intel display when does it go black? Is this a recent regression or has it been broken for a while? Can you post the graphics section of about:support?

(Inlining images somehow doesn't work here...

Graphics Section P1

Graphics Section P2

Graphics Section P3

When I drag a window to the Intel attached display, then it goes black in the same moment as I release the mouse from window for dragging. Theoretically, I could prevent it from going black, if I keep dragging the window.

Well, I reported this 18 days ago, so it is going on now 18 days + a couple of weeks maybe. It started exactly at the time when I enabled SLI on my system. Before that, no problem like that occured.

Can you confirm that if you disable SLI and are only using 3 monitors it doesn't happen for you?

(In reply to Jeff Muizelaar [:jrmuizel] from comment #5)

Can you confirm that if you disable SLI and are only using 3 monitors it doesn't happen for you?

Well, seems like the bug was on nVIDIA's side. I updated my graphics driver and the issue is solved. Thanks for the help, anyway. You may close this issue.

Reading through their changelog, it might have something to do with issue #2453059, mentioned on page 12 of the current driver version's release notes.

Per OP comment #6, I'm closing this bug as WORKSFORME.