If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Menus appear transparent when hardware acceleration is enabled

UNCONFIRMED
Unassigned

Status

()

Core
Graphics
UNCONFIRMED
3 years ago
3 years ago

People

(Reporter: Dominik Neumeister, Unassigned)

Tracking

33 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0
Build ID: 20141106120505

Steps to reproduce:

Opening the contextmenu or an entry from the menubar results in transparent menu with "shadow" border. This also affects the adressfield, searchfield, bookmarklist next to the searchfield, folders in the bookmarklist and drop down lists in websites.

Very rarly, one random entry from the menubar or the bookmark list is visible.

Reinstalling Firefox (tried both version 31 which definitely worked and version 33) with a clean new profile didn't solve the problem.
Making a system recovery on Windows doesn't solve it either.

If I turn off hardware acceleration in the FF settings, everything works fine.

Update: I tried to make a screenshot of this behavior but when I'm hitting the "print" key the menues appear.

I'm using Windows 7 Enterprise SP1 64bit with AMD Radeon HD 7400M Series and the latest stable driver from the catalyst control center.


Actual results:

When hardware acceleration is enabled, menus are shown transparent.


Expected results:

Menu entries should be displayed.

Comment 1

3 years ago
Could you attach a screenshot of the graphics issue, please.

In addition, type about:support in the location bar and paste in your message the "graphics" section.
Component: Untriaged → Graphics
Flags: needinfo?(domar)
Product: Firefox → Core
(Reporter)

Comment 2

3 years ago
Graphics
Direct2D activated	true
DirectWrite activated	true (6.2.9200.16571)
Device-ID	0x6760
GPU #2 active	false
GPU-accelerated windows	2/2 Direct3D 11 (OMTC)
GPU-Description	AMD Radeon HD 7400M Series
Video-RAM	1024
GPU-Driver	aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64
Driver-Date	9-29-2014
Driver-Version	14.301.1001
Vendor-ID	0x1002
WebGL-Renderer	Google Inc. -- ANGLE (AMD Radeon HD 7400M Series Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote	true
AzureCanvasBackend	direct2d
AzureContentBackend	direct2d
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0
Flags: needinfo?(domar)
(Reporter)

Comment 3

3 years ago
Created attachment 8528241 [details]
firefox_bug.jpg

Comment 4

3 years ago
If FF31 worked but not FF33, could you install the tool mozregression to find a regression range, please.
See http://mozilla.github.io/mozregression/

FF31 nightlies started in March 2014, so --good=2014-03-01 is a good start.
No need to bisect, just copy the console outpout when you have the good and the bad builds with the pushlog.
Flags: needinfo?(domar)
Keywords: regressionwindow-wanted
(Reporter)

Comment 5

3 years ago
Got as far as we can go bisecting nightlies...
Ensuring we have enough metadata to get a pushlog...
Last good revision: cb9f34f73ebe (2014-05-20)
First bad revision: 9d8d16695f6a (2014-05-21)
Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=cb9f34f73ebe&tochange=9d8d16695f6a

... attempting to bisect inbound builds (starting from previous week, to make sure no inbound revision is missed)
Getting http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2014/05/2014-05-13-03-02-01-mozilla-central/firefox-32.0a1.en-US.win64-x86_64.txt
Getting inbound builds between 4b6d63b05a0a and 9d8d16695f6a
Traceback (most recent call last):
  File "c:\mozilla-build\python\Scripts\mozregression-script.py", line 8, in <module>
    load_entry_point('mozregression==0.25', 'console_scripts', 'mozregression')()
  File "build\bdist.win32\egg\mozregression\regression.py", line 365, in cli
  File "build\bdist.win32\egg\mozregression\regression.py", line 363, in <lambda>
  File "build\bdist.win32\egg\mozregression\regression.py", line 208, in bisect_nightlies
  File "build\bdist.win32\egg\mozregression\regression.py", line 205, in bisect_nightlies
  File "build\bdist.win32\egg\mozregression\regression.py", line 208, in bisect_nightlies
  File "build\bdist.win32\egg\mozregression\regression.py", line 208, in bisect_nightlies
  File "build\bdist.win32\egg\mozregression\regression.py", line 205, in bisect_nightlies
  File "build\bdist.win32\egg\mozregression\regression.py", line 208, in bisect_nightlies
  File "build\bdist.win32\egg\mozregression\regression.py", line 205, in bisect_nightlies
  File "build\bdist.win32\egg\mozregression\regression.py", line 205, in bisect_nightlies
  File "build\bdist.win32\egg\mozregression\regression.py", line 208, in bisect_nightlies
  File "build\bdist.win32\egg\mozregression\regression.py", line 176, in bisect_nightlies
  File "build\bdist.win32\egg\mozregression\regression.py", line 107, in bisect_inbound
AttributeError: 'NoneType' object has no attribute 'app'

Thank you for the hint with the mozregression tool. Didn't know that before.
Unluckily, I didn't get detailed information (see the traceback above). Otherwise I would have tried to do the bisect by myself.
Flags: needinfo?(domar)
(Reporter)

Updated

3 years ago
Keywords: regressionwindow-wanted
You need to log in before you can comment on or make changes to this bug.