1207397 - Visual corruption in the title and tab bar

Status: RESOLVED WORKSFORME

(Core :: Graphics, defect, P3)

Description

[Casper Braschi]

Attachment: Firefox-chrome-issue-2.gif

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20150921004016

Steps to reproduce:

I have this issue with my installation on Windows 10. The chrome has a drawing problem as well as an old Windows shell rendering.
I was expecting it to be solved after upgrading to 41, but that didn't happen.

That doesn't happen with my Dev version install.



Actual results:

The tab-bar section will draw the tabs over the window shell only after hovering the mouse.
The controls - scroll-bars, modals etc - are not rendered as a Windows 10 themed shell, but as the fallback old shell appearance.

Things I've tried so far to solve this:

• turning on/off hardware acceleration;
• update, reinstall and fresh install;
• opening on safe mode;
• refreshing profile;
• changing themes;

Comment 1

[Loic]

Please, type about:support in the location bar and copy here the section "graphics".

Comment 2

[Casper Braschi]

(In reply to Loic from comment #1)
> Please, type about:support in the location bar and copy here the section
> "graphics".

Here you go:

Graphics
--------

Adapter Description: AMD Radeon HD 7310 Graphics
Adapter Drivers: aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64
Adapter RAM: 384
Asynchronous Pan/Zoom: none
Device ID: 0x9809
DirectWrite Enabled: false (10.0.10240.16430)
Driver Date: 8-3-2015
Driver Version: 15.200.1062.1004
GPU #2 Active: false
GPU Accelerated Windows: 0/1 Basic (OMTC)
Subsys ID: 2af2103c
Supports Hardware H264 Decoding: false
Vendor ID: 0x1002
WebGL Renderer: Google Inc. -- ANGLE (AMD Radeon HD 7310 Graphics Direct3D11 vs_5_0 ps_5_0)
windowLayerManagerRemote: true
AzureCanvasBackend: skia
AzureContentBackend: cairo
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0

Comment 3

[Bas Schouten (:bas.schouten)]

Are you always seeing this? I've seen bugs like this occur from time to time after a driver reset or something else that sends windows into a messed up state.. But not from just starting up firefox. Considering the type of artifact and the acceleration independence I suspect this is a widget bug rather than a graphics bug.

Comment 4

[Casper Braschi]

I see this on Firefox every time I open it.

Comment 5

[(No longer employed by Mozilla) Aaron Klotz]

(In reply to Bas Schouten (:bas.schouten) from comment #3)
> Are you always seeing this? I've seen bugs like this occur from time to time
> after a driver reset or something else that sends windows into a messed up
> state.. But not from just starting up firefox. Considering the type of
> artifact and the acceleration independence I suspect this is a widget bug
> rather than a graphics bug.

I agree. My money is on DWM.

Comment 6

[Casper Braschi]

Just to get it right. 
Don't both stable and developer edition use the "same" DWM?
If they do, why is it happening only to my stable version?

As for "[...] But not from just starting up firefox", I think you are assuming that it happens to all windows and all applications. 
It happens only with my regular Firefox version.

As an additional information, today I opened a window just to see if the problem was gone, and the previous installed theme (the one I stalled for debugging purposes) showed up, even though it was not even installed.

Comment 7

[u279076]

Please check the following:
Does this bug reproduce with the current version (49.0.1 as of this comment)?
Does this bug reproduce with the current Nightly version (52.0a1 as of this comment)?
Does this bug reproduce if you turn off multi-process in the current Nightly version?
Does this bug reproduce if you use the default Windows theme and default Firefox theme? 
Does this bug reproduce with any version of Firefox prior to Firefox 41?

Thanks

Comment 8

[Casper Braschi]

(In reply to Anthony Hughes (:ashughes) [GFX][QA][Mentor] from comment #7)

Thank you, Anthony.

> Please check the following:
> Does this bug reproduce with the current version (49.0.1 as of this comment)?

Yes.

> Does this bug reproduce with the current Nightly version (52.0a1 as of this
> comment)?

No.

> Does this bug reproduce if you turn off multi-process in the current Nightly
> version?

The checkbox is grayed out. 

> Does this bug reproduce if you use the default Windows theme and default
> Firefox theme? 

I don't have any other themes installed on Firefox.
No changes with the default Windows theme.

> Does this bug reproduce with any version of Firefox prior to Firefox 41?

It didn't, but now I tested until version 37.0 and it was there. So I guess it's environmental.

Comment 9

[Casper Braschi]

The title "Visual corruption in the title and tab bar" might be inappropriate as the bug seems to extend to the whole window; see the scrollbars and dialogue in my attachment.

As a side note, I installed the x64 version here and it all seems ok with it.

Comment 10

[u279076]

(In reply to Casper Braschi from comment #9)
> As a side note, I installed the x64 version here and it all seems ok with it.

Hmm, so this might be a bug specifically with the 32-bit build, or maybe this is an out-of-memory bug. Either way, please continue testing the 64-bit build and see if it shows up. Also, it would be good to get a fresh copy of about:support#Graphics, if you could please provide a copy from Release and from Nightly so we can compare.

I'm not sure why multiprocess is greyed out as it is not greyed out for me. You should be testing this on a new profile as jumping between Nightly and Release builds on the same profile can sometimes result in strange behaviour.

Comment 11

[Casper Braschi]

Just to inform that the issue is gone as of 50.1.0, at least. Can't confirm on previous versions.