1059804 - [OMTC] [Direct3D9] Titlebar fog overlays Windows command buttons

Status: VERIFIED WONTFIX

(Core :: Graphics: Layers, defect)

Description

[Jim Mathies [:jimm]]

Attachment: titlebar-maximized.png

This is on a Windows 7 laptop with a wide screen aspect ratio. Its a permanent issue I see when the browser window is maximized. 

Pretty sure this is probably a dupe, but I couldn't find anything via bugzilla.

Tested using latest nightly.

Comment 1

[Jim Mathies [:jimm]]

Attachment: titlebar-maximized.png

smaller screenshot of the affected area.

Comment 2

[:Gijs (he/him)]

(In reply to Jim Mathies [:jimm] from comment #0)
> Created attachment 8480587 [details]
> titlebar-maximized.png
> 
> This is on a Windows 7 laptop with a wide screen aspect ratio. Its a
> permanent issue I see when the browser window is maximized. 
> 
> Pretty sure this is probably a dupe, but I couldn't find anything via
> bugzilla.

Actually, I'm fairly sure this is a regression... this used to work. :-\

Comment 3

[Jim Mathies [:jimm]]

On my main workstation I can't reproduce this. Maybe it has something to do with the aspect ratio of the display.

Comment 5

[:Gijs (he/him)]

Jim, can you still reproduce this? What are the graphics details of the machine where you see this?

gotyaoi, can you provide the details of the NVIDIA GTX 760 machine (about:support, just the graphics section)

Thank you!

Comment 6

[gotyaoi]

Sure, no problem.

Adapter Description	NVIDIA GeForce GTX 760
Adapter Drivers	nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Adapter RAM	2048
ClearType Parameters	Gamma: 2200 Pixel Structure: R ClearType Level: 50 Enhanced Contrast: 100
Device ID	0x1187
Direct2D Enabled	true
DirectWrite Enabled	true (6.2.9200.16492)
Driver Date	9-13-2014
Driver Version	9.18.13.4411
GPU #2 Active	false
GPU Accelerated Windows	2/2 Direct3D 11 (OMTC)
Vendor ID	0x10de
WebGL Renderer	Google Inc. -- ANGLE (NVIDIA GeForce GTX 760 Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote	true
AzureCanvasBackend	direct2d
AzureContentBackend	direct2d
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0

Comment 7

[:Gijs (he/him)]

Milan, looks like this is essentially the same problem as bug 1089312, but a driver from september of this year... can you have a look?

Comment 8

[Milan Sreckovic [:milan] (needinfo for best results)]

Bug 1089312 has some extra theme stuff, right?  Jim, what is the resolution of the laptop?  Buttons work, but look inactive?  This only happens when maximized, or also when you resize Firefox to fill the full screen?  Also, that bug has add-on FlashOnOff which makes the problem go away when disabled - any add-ons in this setup?

Comment 9

[gotyaoi]

A couple notes about what I've tried in the last few days. For the record, resolution is 1920x1080, only add-on is firebug and it only seems to happen while maximized:

1. Turning off either HWA or OMTC or both stops symptoms from appearing.

2. Turning off only OMTC causes quite a few rendering errors, such as black boxes in text areas, pdf.js, google maps, twitter and other things.

3. On the older machine (driver ~2012), the buttons are permanently fogged, but there do not seem to be further effects. On the newer machine, issues are much rarer, but more spectacular when they do happen. Basically, first, the interface will stop visually updating except for the menu. Clicking still changes the window title for example, but nothing changes within the window. This may go away after a few minutes, but it starts happening with more frequency over time. Finally, any open windows will go completely white. I can still click on where things should be to get some effects, like changing the window title or showing the menu (which renders over the white), but no visual indications aside from that. I'm still able to open new windows, which do render, but now have the fog overlapping the buttons. This persists until firefox is restarted.

HTH

Comment 10

[Jim Mathies [:jimm]]

Attachment: support.txt

(In reply to :Gijs Kruitbosch from comment #5)
> Jim, can you still reproduce this? What are the graphics details of the
> machine where you see this?

yes. this laptop is basically dead to me, if you want I can clean it up and ship it somewhere, or help debug from here I guess if you can point me to something I can test/debug.

Comment 11

[:Gijs (he/him)]

(In reply to Jim Mathies [:jimm] from comment #10)
> Created attachment 8522232 [details]
> support.txt

Venkman! <3
:-)

(but, these drivers seem to be a lot older. :-( )

> (In reply to :Gijs Kruitbosch from comment #5)
> > Jim, can you still reproduce this? What are the graphics details of the
> > machine where you see this?
> 
> yes. this laptop is basically dead to me, if you want I can clean it up and
> ship it somewhere, or help debug from here I guess if you can point me to
> something I can test/debug.

I think it'd be super helpful to just have a regression window from mozregression, and/or answers to the questions in comment #8. Same goes for [e-mail], by the way. Don't know if the regression windows will be the same considering driver age / chipsets at issue...

Otherwise I defer to Milan - I am just some frontend guy who's annoyed that we're shipping this bug with the titlebar fog again. We harassed the hell out of the graphics and windows folks - sorry to both you and Milan / Matt Woodrow! - to get rid of it for 29/30 and now it's back... In any case, I am likely to be useless in terms of debugging the actual graphics code issues causing this. Sorry!

Comment 12

[Milan Sreckovic [:milan] (needinfo for best results)]

Jim, yes, please, ship it to me in the Toronto Mozilla office.  Make sure it still reproduces once you clean it up :), but it would be a great help to have it.  If shipping it is complicated, bring it to Portland, although that misses another train...

Comment 13

[Jim Mathies [:jimm]]

I just noticed I have two prefs set - 

layers.acceleration.force-enabled: true
layers.prefer-d3d9: true

The support data says acceleration is disabled. Wondering if I've introduced this through these prefs?

Comment 14

[Jim Mathies [:jimm]]

> layers.prefer-d3d9: true

resetting this fixes the problem.

milan, if you still want this shipped, let me know. it's no problem, I can have it to you next week.

Comment 15

[Milan Sreckovic [:milan] (needinfo for best results)]

OK, I'll leave it to Bas to decide then.  Bas, can we get into the state that Jim was in "naturally"?

Comment 16

[Bas Schouten (:bas.schouten)]

(In reply to Jim Mathies [:jimm] from comment #14)
> > layers.prefer-d3d9: true
> 
> resetting this fixes the problem.
> 
> milan, if you still want this shipped, let me know. it's no problem, I can
> have it to you next week.

This shouldn't really be a concern, the D3D9 Compositor should never be used on Windows 7+ where this problem may occur.

Comment 17

[Jim Mathies [:jimm]]

Sounds like this is wontfix per comment 16.

Comment 18

[Jeff Muizelaar [:jrmuizel]]

Couldn't this happen on Vista?

Comment 19

[Jim Mathies [:jimm]]

This also reproduces in safe mode for me on the same system without those custom d3d9 settings.

Comment 20

[Jim Mathies [:jimm]]

Milan, you might want to re-triage this one to be sure we haven't missed something.

Comment 21

[Milan Sreckovic [:milan] (needinfo for best results)]

Jim, in the safe mode with the latest nightly?

Comment 22

[Jim Mathies [:jimm]]

(In reply to Milan Sreckovic [:milan] from comment #21)
> Jim, in the safe mode with the latest nightly?

yeah, just happened to land in safe mode today, noticed the fog overlays the lower part of the command buttons for some reason. I'll post a screenshot and double check my prefs too.

Comment 23

[Jim Mathies [:jimm]]

Attachment: safemode win7.png

Safe mode gfx info:

Adapter Description: NVIDIA GeForce GTX 660 Ti
Adapter Drivers: nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Adapter RAM: 2048
Asynchronous Pan/Zoom: wheel input enabled
ClearType Parameters: Gamma: 2200 Pixel Structure: R ClearType Level: 50 Enhanced Contrast: 50
Device ID: 0x1183
DirectWrite Enabled: false (6.2.9200.16571)
Driver Date: 2-5-2015
Driver Version: 9.18.13.4752
GPU #2 Active: false
GPU Accelerated Windows: 0/1 Basic (OMTC)
Subsys ID: 100010de
Vendor ID: 0x10de
WebGL Renderer: Google Inc. -- ANGLE (NVIDIA GeForce GTX 660 Ti Direct3D11 vs_5_0 ps_5_0)
windowLayerManagerRemote: true
AzureCanvasBackend: skia
AzureContentBackend: cairo
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0

Comment 24

[Jim Mathies [:jimm]]

looks like a layout/xul problem vs. a gfx problem, imho.

Comment 25

[:Gijs (he/him)]

(In reply to Jim Mathies [:jimm] from comment #24)
> looks like a layout/xul problem vs. a gfx problem, imho.

Safe mode is covered by bug 966936. May or may not be the same issue.