Open Bug 1339048 Opened 9 years ago Updated 3 years ago

Firefox windows go blank when moving across screens with different scale levels on Windows 10

Categories

(Core :: Graphics, defect)

51 Branch
x86_64
Windows 10
defect

Tracking

()

UNCONFIRMED

People

(Reporter: github.guy, Unassigned)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce: Dragging, or <Alt>+<Tab>ing, a Firefox window between monitors - which are at different scale settings, 150%-100%-125% Actual results: Sometimes results in the window becoming blank! Expected results: Window should "scale" appropriately
Just had another thought regarding this problem! The left two screens are managed by nVidia whilst the right-hand [laptop] screen is Intel HD. However, no other applications seem to be suffering with the problem so far - only Firefox.
Could you type about:support and copy here the section "graphics". Does it work if you disable HWA in Firefox? http://support.mozilla.org/en-US/kb/forum-response-disable-hardware-acceleration
Component: Untriaged → Graphics
Flags: needinfo?(github.guy)
OS: Unspecified → Windows 10
Product: Firefox → Core
Hardware: Unspecified → x86_64
Graphics Features Compositing Direct3D 11 Asynchronous Pan/Zoom none WebGL Renderer Google Inc. -- ANGLE (NVIDIA Quadro K1100M Direct3D11 vs_5_0 ps_5_0) WebGL2 Renderer Google Inc. -- ANGLE (NVIDIA Quadro K1100M Direct3D11 vs_5_0 ps_5_0) Hardware H264 Decoding Yes; Using D3D11 API Audio Backend wasapi Direct2D true DirectWrite true (10.0.14393.351) GPU #1 Active Yes Description NVIDIA Quadro K1100M Vendor ID 0x10de Device ID 0x0ff6 Driver Version 10.18.13.5362 Driver Date 7-22-2015 Drivers nvd3dumx,nvwgf2umx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um,nvwgf2um Subsys ID 221a17aa RAM 2048 GPU #2 Active No Description Intel(R) HD Graphics 4600 Vendor ID 0x8086 Device ID 0x0416 Driver Version 20.19.15.4474 Driver Date 6-13-2016 Drivers igdumdim64 igd10iumd64 igd10iumd64 igd12umd64 igdumdim32 igd10iumd32 igd10iumd32 igd12umd32 Subsys ID 221e17aa RAM Unknown Diagnostics ClearType Parameters DISPLAY4 [ Gamma: 2.2 Pixel Structure: RGB ClearType Level: 50 Enhanced Contrast: 0 ] DISPLAY5 [ Gamma: 2.2 Pixel Structure: BGR ClearType Level: 0 Enhanced Contrast: 100 ] DISPLAY9 [ Gamma: 2.2 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 0 ] AzureCanvasAccelerated 0 AzureCanvasBackend direct2d 1.1 AzureContentBackend direct2d 1.1 AzureFallbackCanvasBackend cairo ClearType Parameters DISPLAY4 [ Gamma: 2.2 Pixel Structure: RGB ClearType Level: 50 Enhanced Contrast: 0 ] DISPLAY5 [ Gamma: 2.2 Pixel Structure: BGR ClearType Level: 0 Enhanced Contrast: 100 ] DISPLAY9 [ Gamma: 2.2 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 0 ] Decision Log D3D9_COMPOSITING disabled by default: Disabled by default
I've a work around for the problem too! If I create a new tab in the blank window (<Ctrl>+t) then I can *drag* the first tab out of the blank window and its all good!
It *does* look to be related to HW acceleration! I'm sure that I tried previously, but maybe I didn't do a full FF restart. So, WITHOUT HW acceleration looks like it free from this issue - which ties in nicely with the split video HW support Intel for the laptop screen vs nVidia for the [larger] Display Port attached screens.
Flags: needinfo?(github.guy)
IMHO, you should update your drivers, especially with Win 10. Both drivers (Nvidia and Intel) are pre-anniversary update for Win 10and are known to be buggy.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: