1254463 - Visual glitches in menus with intel drivers

Status: RESOLVED WORKSFORME

(Core :: Graphics, defect)

Description

[u428464]

On my XPS 13 (200% dpi on Windows 10), when I open a bookmarks folder in the bookmarks toolbar, there are often visual glitches (black zones) that pop up here. It seems to be dpi related since it doesn't happen on my main build that is at 100%.

Comment 1

[u428464]

May be related to bug 1238340.

Comment 2

[:Gijs (he/him)]

(In reply to Guillaume C. [:ge3k0s] from comment #0)
> It seems to be dpi related since it doesn't happen on my main build
> that is at 100%.

Is the main build also running on win10 ?

Black boxes are pretty much never theme-related, and almost always a gfx issue.

Can you provide the about:support gfx info from both the working and non-working places?

Does turning off hardware acceleration fix the issue on the hidpi machine?

Comment 3

[u428464]

(In reply to :Gijs Kruitbosch from comment #2)
> (In reply to Guillaume C. [:ge3k0s] from comment #0)
> > It seems to be dpi related since it doesn't happen on my main build
> > that is at 100%.
> 
> Is the main build also running on win10 ?

Yes.
> Black boxes are pretty much never theme-related, and almost always a gfx
> issue.
>
> Can you provide the about:support gfx info from both the working and
> non-working places?

I'm not at home but here are the graphic info on my hidpi build :

Graphics
Adapter Description	Intel(R) HD Graphics 5500
Adapter Drivers	igdumdim64 igd10iumd64 igd10iumd64 igd12umd64 igdumdim32 igd10iumd32 igd10iumd32 igd12umd32
Adapter RAM	Unknown
Asynchronous Pan/Zoom	none
Device ID	0x1616
Direct2D Enabled	true
DirectWrite Enabled	true (10.0.10586.0)
Driver Date	11-18-2015
Driver Version	20.19.15.4331
GPU #2 Active	false
GPU Accelerated Windows	1/1 Direct3D 11 (OMTC)
Subsys ID	06651028
Supports Hardware H264 Decoding	Yes
Vendor ID	0x8086
WebGL Renderer	Google Inc. -- ANGLE (Intel(R) HD Graphics 5500 Direct3D11 vs_5_0 ps_5_0)
windowLayerManagerRemote	true
AzureCanvasBackend	direct2d 1.1
AzureContentBackend	direct2d 1.1
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0

> Does turning off hardware acceleration fix the issue on the hidpi machine?

Yes it seems to solve it. Also note that the problem occurs with 100% dpi too on this config.

Comment 4

[:Gijs (he/him)]

Pinging gfx folks for comment #3.

(Milan, please do let me know if new bugzilla focus stuff means I should just assume things will get looked at once moved into Core::Graphics and to stop needinfo'ing you :-) )

Comment 5

[u428464]

I must admit I'm not sure it's dpi related anymore.

Comment 6

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

(In reply to :Gijs Kruitbosch from comment #4)
> Pinging gfx folks for comment #3.
> 
> (Milan, please do let me know if new bugzilla focus stuff means I should
> just assume things will get looked at once moved into Core::Graphics and to
> stop needinfo'ing you :-) )

Yes, please, CC me on bugs that move into graphics, especially when they are older than a week when this move happens.  And use needinfo when you need more than to call my attention to it.

Comment 7

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

(In reply to Guillaume C. [:ge3k0s] from comment #5)
> I must admit I'm not sure it's dpi related anymore.

I'm guessing it could be related to bug 1253241.  Any chance you could get a regression range using mozregression (http://mozilla.github.io/mozregression/)?

Comment 8

[u428464]

(In reply to Milan Sreckovic [:milan] (PTO until 3/23) from comment #7)
> (In reply to Guillaume C. [:ge3k0s] from comment #5)
> > I must admit I'm not sure it's dpi related anymore.
> 
> I'm guessing it could be related to bug 1253241.  Any chance you could get a
> regression range using mozregression
> (http://mozilla.github.io/mozregression/)?

I will try in the next few days but I don't know if I'll find time to do it. FWIW the bug happens with e10s disabled and doesn't look like the screencast in bug 1253241.

Comment 9

[u428464]

I'm beginning to wonder if it's not related to intel drivers. Philipp IIRC you also have an XPS13. Could you try to reproduce this issue ? FWIW I'm on the first new gen of XPS13 (9343).

Comment 10

[(Currently slow to respond) Philipp Sackl [:phlsa] (Firefox UX) please use needinfo]

I've had the same issues on an XPS13 and a Surface Pro, both of which (I think) have Intel grpahics.
The issues have been gone for me since bug 1245765 landed in Nightly. They are still present in the release version.
Could you try to reproduce with a current Nightly?

Comment 11

[u428464]

(In reply to Out of office until March 28! Philipp Sackl [:phlsa] (Firefox UX) please use needinfo from comment #10)
> I've had the same issues on an XPS13 and a Surface Pro, both of which (I
> think) have Intel grpahics.
> The issues have been gone for me since bug 1245765 landed in Nightly. They
> are still present in the release version.
> Could you try to reproduce with a current Nightly?

Yes the issue seems to be still present in latest Nightly. The windows repaint issue doesn't seem to be reproducible anymore, but the black glitches in menus appear from time to time.

Comment 12

[u428464]

Ok I've done a clean install of the last Intel drivers on my PC and the issue seems to be gone. I will wait a bit and close the bug in a few days if it's the case.

Comment 13

[u428464]

So my drivers were clearly corrupted. Sorry for the unnecessary noise here.

Comment 14

[u428464]

Ok for some unknown reasons the issue has reappeared...

Comment 15

[u428464]

I'm wondering whether it's related to the fact that a plugin (Flash player) is present on the page. It seems to happen only at this condition.

Comment 16

[David Bolter [:davidb] (NeedInfo me for attention)]

Can you still reproduce this issue? (We think it might be fixed)

Comment 17

[u428464]

(In reply to David Bolter [:davidb] from comment #16)
> Can you still reproduce this issue? (We think it might be fixed)

I've seen it recently a couple of times on Firefox 49, but I haven't tested Nighlty in a long while.

Comment 18

[u428464]

Can't reproduce anymore