1158827 - [D2D] lack of hwa on computer with GeForce 7300 SE/7200 GS

Status: UNCONFIRMED

(Core :: Graphics, defect)

Description

[aquila]

Attachment: about_support_xp.txt

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0
Build ID: 20150415140819

Steps to reproduce:

Recently I've switched from Win XP to Win 7 and after that hardware acceleration in Firefox is disabled. Scrolling complex sites is visibly slower than it was on Win XP with hwa enabled. I've tried to force hwa by setting gfx.direct2d.force-enabled to true, but nothing changed.  I'm attaching content of about:support from both systems and also informations from sxdiag utility

Comment 1

[aquila]

Attachment: about_support_7.txt

Comment 2

[aquila]

Attachment: DxDiag.txt

Comment 3

[aquila]

Attachment: gpu.html

I'm also attaching about:gpu from chrome. It seems that they manage to hardware accelerate most of things on my machine.

Comment 4

[David Anderson [:dvander] - inactive, e-mail if emergency]

(In reply to aquila from comment #3)
> Created attachment 8646282 [details]
> gpu.html
> 
> I'm also attaching about:gpu from chrome. It seems that they manage to
> hardware accelerate most of things on my machine.

What does about:support look like from a newer version of Firefox? (Say, Dev Edition, but 40+ works too.)

Comment 5

[aquila]

Attachment: about_support_nightly_09_2015.txt

Here's one from today's Nightly

Comment 6

[David Anderson [:dvander] - inactive, e-mail if emergency]

(In reply to aquila from comment #5)
> Created attachment 8661752 [details]
> about_support_nightly_09_2015.txt
> 
> Here's one from today's Nightly

Weird, I would expect some kind of reason in there. Out of curiosity, could you go to about:telemetry, expand the "Environment Data" section, then go to "system" - and copy+paste everything under "gfx.features"?

Comment 7

[aquila]

Sure. It looks like this:

gfx.features.compositor 	basic
gfx.features.d3d11.status 	available
gfx.features.d3d11.version 	37632
gfx.features.d3d11.warp 	false
gfx.features.d3d11.textureSharing 	false
gfx.features.d3d11.blacklisted 	false
gfx.features.d2d.status 	failed
gfx.features.d2d.version 	1.0

Comment 8

[David Anderson [:dvander] - inactive, e-mail if emergency]

It looks like D2D has no chance of working on this system (indeed, Chrome doesn't appear to be using it either). But D3D11 compositing should be working, so it's strange that it's not being used. If you create a fresh profile do you see the same thing?

Comment 9

[aquila]

Yes, it looks the same on the fresh profile:

gfx.D2DEnabled 	false
gfx.DWriteEnabled 	false
gfx.adapters.[0].description 	NVIDIA GeForce 7300 SE/7200 GS
gfx.adapters.[0].vendorID 	0x10de
gfx.adapters.[0].deviceID 	0x01d3
gfx.adapters.[0].subsysID 	00000000
gfx.adapters.[0].RAM 	256
gfx.adapters.[0].driver 	nvd3dumx,nvd3dum
gfx.adapters.[0].driverVersion 	9.18.13.908
gfx.adapters.[0].driverDate 	1-30-2015
gfx.adapters.[0].GPUActive 	true
gfx.monitors.[0].screenWidth 	1680
gfx.monitors.[0].screenHeight 	1050
gfx.monitors.[0].refreshRate 	59
gfx.monitors.[0].pseudoDisplay 	false
gfx.features.compositor 	basic
gfx.features.d3d11.status 	available
gfx.features.d3d11.version 	37632
gfx.features.d3d11.warp 	false
gfx.features.d3d11.textureSharing 	false
gfx.features.d3d11.blacklisted 	false
gfx.features.d2d.status 	failed
gfx.features.d2d.version 	1.0 

Maybe title of this bug should be changed if it's not a D2D issue?
I'm also wondering if the fact that on win XP (where hwa worked) I had older version of geforce drivers, could matter. Maybe there's something wrong with new ones, or maybe they are just broken for win 7?

Comment 10

[David Anderson [:dvander] - inactive, e-mail if emergency]

Having looked at a similar bug recently, I have a guess: we probably succeeded in creating an initial D3D11 device, but later when we went to create a compositor for the window, it failed to initialize all of its state from the D3D11 device. Unfortunately there's like 30 things that could fail to get initialized and we don't really log any of them. But this would cause you to see D3D11 as "available" but not actually get used.

If nVidia has newer drivers for your card, you could try updating. Other than that I doubt there's much we can do.

Comment 11

[aquila]

Thanks for information. I'll wait for new drivers from nvidia or experiment with downgrading them to check if this problem occured in older versions.

I wonder if more verbose logging of gfx issues like about:gpu in chrome would be a good addition to firefox.

btw I noticed this in about:gpu
Log Messages
[6972:6320:0930/101623:ERROR:gl_surface_egl.cc(486)] : eglInitialize D3D11 failed with error EGL_NOT_INITIALIZED, trying next display type

which I think confirms your guess

Comment 12

[aquila]

Attachment: support_nightly_17_11_2015

In today's nightly I noticed that in about:support new section appeared:
(#0) Error	[D3D11] create component blender failed: 0x80070057

I doubt it has something to do with lack of hwa, but I'm adding it here just for information. I'm about to change my workstation to new one and I'm pretty sure Firefox will work with hwa well on it.