1269843 - Graphical Issue [Win 10 + Firefox 46.0] : calling Firefox from taskbar or resizing it.

Status: UNCONFIRMED

(Core :: Graphics, defect, P3)

Description

[linkinpark99]

Attachment: Desktop_Screenshot2_03_05_2016_privacy.jpg

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0
Build ID: 20160421124000

Steps to reproduce:

Hi,
first things first: I've got Win 10 Pro ( Vers. 1511, Build: 10586.218, 64-bit).
My onboard graphic-chip as well as my NVIDIA graphiccard are both up to date (checked that).
Firefox is up-to-date as well (as far as I know - V. 46.0).
Problem:
If Firefox is only minimized to taskbar and then opened again, it will stay blank. In this "Stage" I'm able to hover right above the "Data | Edit | View" menue which results in displaying these elements again - ONLY these elements.

With Firefox in fullscreen-mode : trying to resize firefox will lead to a graphical issue by displaying some "glitched" area / testfields.

This only happens to me while using Firefox, every single App beside Firefox is working just fine. I remember it happening scince I've updated to Win10, but I'm not sure - sorry.

the red part in the screenshot is by myself - thats not caused by the glitch/problem

regards


Actual results:

see above


Expected results:

no graphical glitch should appear as far as I know firefox.

Comment 1

[Loic]

could you copy here the graphics section of the page about:support, please.

is it better with HWA disabled?
https://support.mozilla.org/en-US/kb/forum-response-disable-hardware-acceleration

Comment 2

[linkinpark99]

Hi,

sorry for the late response. Here is the the content from about:support -> graphic section:

Asynchrones Wischen und Zoomen	nichts
Direct2D aktiviert	true
DirectWrite aktiviert	true (10.0.10586.0)
Gerätekennung	0x191b
Gerätekennung (GPU #2)	0x1427
GPU #2 aktiv	false
GPU-beschleunigte Fenster	1/1 Direct3D 11 (OMTC)
H264-Hardware-Dekodierung unterstützt	Yes
Herstellerkennung	0x8086
Herstellerkennung (GPU #2)	0x10de
Karten-Beschreibung	Intel(R) HD Graphics 530
Karten-Beschreibung (GPU #2)	NVIDIA GeForce GTX 965M
Karten-RAM	Unknown
Karten-RAM (GPU #2)	2048
Karten-Treiber	igdumdim64 igd10iumd64 igd10iumd64 igd12umd64 igdumdim32 igd10iumd32 igd10iumd32 igd12umd32
Karten-Treiber (GPU #2)	nvd3dumx,nvwgf2umx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um,nvwgf2um
Subsys-ID	01521558
Subsys-ID (GPU #2)	01521558
Treiber-Datum	3-23-2016
Treiber-Datum (GPU #2)	3-21-2016
Treiber-Version	20.19.15.4416
Treiber-Version (GPU #2)	10.18.13.6472
WebGL-Renderer	Google Inc. -- ANGLE (Intel(R) HD Graphics 530 Direct3D11 vs_5_0 ps_5_0)
windowLayerManagerRemote	true
AzureCanvasBackend	direct2d 1.1
AzureContentBackend	direct2d 1.1
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0

hope this will help.

Then i just unchecked the HWA option as you suggested - no problems til now; I was unable to reproduce the glitch again after unchecking this feature, maybe contingency, maybe the cause for the problem.

regards ;)

Comment 3

[Loic]

The drivers (intel/nvidia) seem to be up-to-date.

Do you remember if it happened with previous versions of FF?

Comment 4

[linkinpark99]

hi,

yes I can remember it happening before as well (me: " well, test it with the up-to-date version as well, before calling out for a bug" :D ) 
I can't name the prior version though =( sorry.
But my laptop is kinda new and i've installed FF like max. 10 days ago - so the previous version can't be that old anyway.

Comment 5

[u279076]

It's been a couple months, can you please update your Firefox and graphics drivers (both Intel and NVIDIA) to verify the issue persists?