Closed
Bug 626236
Opened 14 years ago
Closed 14 years ago
D3D9 layer acceleration does not work for
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: spammaaja, Unassigned)
Details
(Keywords: regression)
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b9) Gecko/20100101 Firefox/4.0b9
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b10pre) Gecko/20110116 Firefox/4.0b10pre
The pref "layers.prefer-d3d9" disables layer acceleration completely according to about:support.
With layers.prefer-d3d9 false (default):
Adapter Description ATI Radeon HD 4600 Series
Vendor ID 1002
Device ID 9498
Adapter RAM 1024
Adapter Drivers aticfx64 aticfx64 aticfx32 aticfx32 atiumd64 atidxx64 atiumdag atidxx32 atiumdva atiumd6a atitmm64
Driver Version 8.801.0.0
Driver Date
Direct2D Enabled true
DirectWrite Enabled true (6.1.7600.20830)
WebGL Renderer TransGaming Inc. -- ANGLE -- OpenGL ES 2.0 (git-devel Jan 16 2011 04:05:41)
GPU Accelerated Windows 1/1 Direct3D 10
With layers.prefer-d3d9 true:
GPU Accelerated Windows 0/1
(otherwise same)
Reproducible: Always
Actual Results:
GPU Accelerated Windows 0/1
Expected Results:
GPU Accelerated Windows 1/1 Direct3D 9
Keywords: regression,
regressionwindow-wanted
Version: unspecified → Trunk
Comment 1•14 years ago
|
||
About:support says D2D and DW is enabled with D3D9 layers for me.
Regression window:
Working:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101207 Firefox/4.0b8pre
http://hg.mozilla.org/mozilla-central/rev/4d16d58becaf
Not working:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101208 Firefox/4.0b8pre
http://hg.mozilla.org/mozilla-central/rev/95452499f3d6
Pushlog:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=4d16d58becaf&tochange=95452499f3d6
Keywords: regressionwindow-wanted
Could it be caused by this:
aa593835cb8d Bas Schouten — Bug 595277 - Part 4: Delay Direct3D 9 initialization when possible. r=roc a=blocking-final
![]() |
||
Updated•14 years ago
|
blocking2.0: --- → ?
Comment 4•14 years ago
|
||
First, this shouldn't be too hard so it shouldn't be hard to get a patch in.
I don't think this blocks the release though, we've removed D3D9 and D2D interop mode and the combination will now be extremely slow, to the point we're considering to remove this code all together. Disabling D2D will effectively switch you to D3D9/GDI usage.
Comment 5•14 years ago
|
||
The entire set of layers prefs (aside, perhaps, for .acceleration.disable) exist only for testing, and them being broken doesn't block the release.
blocking2.0: ? → -
This affects "gfx.direct2d.disabled" also. If "gfx.direct2d.disabled" is true, there will be no layer acceleration at all. D3D9 is broken completely? Isn't D3D9 + GDI a supported combination?
blocking2.0: - → ?
Summary: The pref "layers.prefer-d3d9" disables layer acceleration completely according to about:support → The pref "layers.prefer-d3d9" or "gfx.direct2d.disabled" disables layer acceleration completely according to about:support
layers.prefer-d3d9;false
gfx.direct2d.disabled;true
GPU Accelerated Windows 0/1
Summary: The pref "layers.prefer-d3d9" or "gfx.direct2d.disabled" disables layer acceleration completely according to about:support → D3D9 layer acceleration does not work
Comment 8•14 years ago
|
||
(In reply to comment #6)
> This affects "gfx.direct2d.disabled" also. If "gfx.direct2d.disabled" is true,
> there will be no layer acceleration at all. D3D9 is broken completely? Isn't
> D3D9 + GDI a supported combination?
Hmm, that's odd, when I disable Direct2D I just get D3D9+GDI.
Comment 9•14 years ago
|
||
Wait a second, did you make sure to load/refresh about:support say, 20-30 seconds after starting firefox?
Summary: D3D9 layer acceleration does not work → D3D9 layer acceleration does not work for
Reporter | ||
Comment 10•14 years ago
|
||
It starts working after about 5 seconds.
Comment 11•14 years ago
|
||
Excellent! That's intended behavior to speed up your start-up time :)
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Updated•14 years ago
|
blocking2.0: ? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•