852751 - Graphics driver block request: ATI R600-R700 for D2D on Windows 7/8

Status: RESOLVED WONTFIX

(Toolkit :: Blocklist Policy Requests, defect)

Description

[Jeff Muizelaar [:jrmuizel]]

OS:     (e.g WINNT 6.1 for Windows 7, Darwin 11 for Mac OS X 10.7, Linux, Android, All)
Vendor:       (0x1002 for ATI)
Devices: 0x9400 0x9401 0x9402 0x9403 0x9405 0x940A 0x940B 0x940F 0x94C0 0x94C1 0x94C3 0x94C4 0x94C5 0x94C6 0x94C7 0x94C8 0x94C9 0x94CB 0x94CC 0x94CD 0x9580 0x9581 0x9583 0x9586 0x9587 0x9588 0x9589 0x958A 0x958B 0x958C 0x958D 0x958E 0x958F 0x9500 0x9501 0x9504 0x9505 0x9506 0x9507 0x9508 0x9509 0x950F 0x9511 0x9515 0x9517 0x9519 0x95C0 0x95C2 0x95C4 0x95C5 0x95C6 0x95C7 0x95C9 0x95CC 0x95CD 0x95CE 0x95CF 0x9590 0x9591 0x9593 0x9595 0x9596 0x9597 0x9598 0x9599 0x959B 0x9610 0x9611 0x9612 0x9613 0x9614 0x9615 0x9616 0x9710 0x9711 0x9712 0x9713 0x9714 0x9715 0x9440 0x9441 0x9442 0x9443 0x9444 0x9446 0x944A 0x944B 0x944C 0x944E 0x9450 0x9452 0x9456 0x945A 0x945B 0x945E 0x9460 0x9462 0x946A 0x946B 0x947A 0x947B 0x9480 0x9487 0x9488 0x9489 0x948A 0x948F 0x9490 0x9491 0x9495 0x9498 0x949C 0x949E 0x949F 0x9540 0x9541 0x9542 0x954E 0x954F 0x9552 0x9553 0x9555 0x9557 0x955F 0x94A0 0x94A1 0x94A3 0x94B1 0x94B3 0x94B4 0x94B5 0x94B9
Feature:     (DIRECT2D)
Feature status:       (BLOCKED_DEVICE)
Driver version:
Driver version comparator:       
Homepage and other references and contact info: 
https://bugzilla.mozilla.org/show_bug.cgi?id=812695
Reasons: Clipping for cleartype text is broken with the IE 10 update.

Comment 1

[Jeff Muizelaar [:jrmuizel]]

OS: Windows 7

Comment 2

[Jeff Muizelaar [:jrmuizel]]

And probably Windows 8 as well.

Comment 3

[Alice0775 White]

I do not understand that block these device.
Because, just bucked out c28cc500c239(Bug 798931) and 13ec2ee2b447(Bug 784382) fixes the problem of bug 812695. See Bug 812695 Comment#71

Comment 4

[Jeff Muizelaar [:jrmuizel]]

(In reply to Alice0775 White from comment #3)
> I do not understand that block these device.
> Because, just bucked out c28cc500c239(Bug 798931) and 13ec2ee2b447(Bug
> 784382) fixes the problem of bug 812695. See Bug 812695 Comment#71

Right but backing out those bugs just trades one problem for another. i.e it moves the bug from D2D back into our code.

Comment 5

[Alice0775 White]

AFAIK, The Bug 784382 is affected to Wndows8 only.

I propose you that

Backed out c28cc500c239(Bug 798931) and 13ec2ee2b447(Bug 784382).
And block these devices for Windwos 8 but not for other OS.

Comment 6

[Jeff Muizelaar [:jrmuizel]]

(In reply to Alice0775 White from comment #5)
> AFAIK, The Bug 784382 is affected to Wndows8 only.
> 
> I propose you that
> 
> Backed out c28cc500c239(Bug 798931) and 13ec2ee2b447(Bug 784382).
> And block these devices for Windwos 8 but not for other OS.

I was under the impression that 784382 will also affect Windows 7 with the IE10 platform update. Do we have evidence that this is not the case?

Comment 7

[Alice0775 White]

Blocking these devices cause will cause Bug 654570 and Bug 671302.
I think that the error of Bug 654570 and Bug 671302 is worse than Bug 784382.

The Bug 784382 is not crash/hang bug. 
And The visibility error of Bug 784382 is not notable than Bug 812695 (I think).

Comment 8

[dusty-2011]

Firefox without Hardware Acceleration is a slow and unstable browser. Page render time is very high, and regularly the entire browser freezes for 10 seconds or more when trying to render a heavy page. With HWA enabled, the same page renders in a few seconds without freezing the browser.
Please reconsider other fixes for Bug 812695, such as turning Azure.content off, before blacklisting old ATI cards. Many users will not be pleased with the decreased performance if HWA is disabled, and will be angry because of the many freezes of the browser that occur with HWA disabled.

Comment 9

[Jeff Muizelaar [:jrmuizel]]

(In reply to Alice0775 White from comment #7)
> Blocking these devices cause will cause Bug 654570 and Bug 671302.
> I think that the error of Bug 654570 and Bug 671302 is worse than Bug 784382.

According to crashstats only 28.5% of our Windows 7 users with these cards are actually using D3D10 layers (D2D). So the vast majority of our users are already experiencing bug 654570 and bug 671302.

Comment 10

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

This needs to be in-code block?

Comment 11

[Jim Taylor]

As I commented in bug 812695 comment 77 ( https://bugzilla.mozilla.org/show_bug.cgi?id=812695#c77 ) I hit the bug after installing KB2670838 Platform Update for Windows 7.

Graphics Chipset      AMD M880G with ATI Mobility Radeon HD 4250
Vendor ID 1002    Device ID 9712

I turned off gfx.content.azure.enabled on 02/28/13 and have had no further problems from that bug or any of the others.  So blocking the driver seems rather heavy handed to me instead of just setting gfx.content.azure.enabled false, or documenting the problem and letting the user do it if they are having the problem.

Comment 12

[Mark Straver]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #9)
> According to crashstats only 28.5% of our Windows 7 users with these cards
> are actually using D3D10 layers (D2D). So the vast majority of our users are
> already experiencing bug 654570 and bug 671302.

Is looking at crashstats a good number? What about all the people that don't have Firefox crash on them and have a smooth running, accelerated system that will be affected as well?

Comment 13

[spam.dump.one]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #9)
> (In reply to Alice0775 White from comment #7)
> > Blocking these devices cause will cause Bug 654570 and Bug 671302.
> > I think that the error of Bug 654570 and Bug 671302 is worse than Bug 784382.
> 
> According to crashstats only 28.5% of our Windows 7 users with these cards
> are actually using D3D10 layers (D2D). So the vast majority of our users are
> already experiencing bug 654570 and bug 671302.

Only? That's 3 users out of 10!

And blocking D2D opens another bug, this one
https://bugzilla.mozilla.org/show_bug.cgi?id=847217

Comment 14

[Jorge Villalobos [:jorgev] (he/him)]

Is this block still needed?

Comment 15

[spam.dump.one]

(In reply to Jorge Villalobos [:jorgev] from comment #14)
> Is this block still needed?

Well, the bug is still there. I'm seeing blurry characters right now on my fully updated laptop.

Just fix the underlaying bug, maybe?

Comment 16

[Arthur K. (he/him)]

Is this even needed now since bug 934860?

Comment 17

[(mostly gone) XtC4UaLL [:xtc4uall]]

Can this get resolved as of now?