Closed Bug 1193654 Opened 9 years ago Closed 9 years ago

Direct2D became disabled in Firefox 40 on Windows 10 today (due to today's Microsoft update KB3081436, I think)

Categories

(Core :: Graphics, defect)

40 Branch
x86_64
Windows 10
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1189940

People

(Reporter: rick3162, Unassigned)

Details

I'm running the latest Nvidia 353.62 drivers for my GTX 780 Ti and while all this time Firefox was working ok in win10 x64, today, after today's Microsoft updates (I suspect KB3081436 -- all others are Office 2013 related), I've noticed tearing while scrolling and some black horizontal lines in inbox.google.gom So I opened `about:support` and here are screenshots: (note the `Blocked for your graphics driver version` entry) Current status: http://i.imgur.com/cQUO0fQ.jpg Previous status: http://i.imgur.com/Dgcngsp.jpg FWIW the VGA appears ok in the Device Manager. And, in my current Firefox profile, in about:preferences#advanced the "use hardware acceleration when available" is enabled of course all the time (I never disabled it). Also, if I restore my profile from backup (i.e the contents from `C:\Users\user\AppData\Roaming\Mozilla`) then Firefox starts without the issue, but unfortunately, after a little time (during the same Firefox session!), the entry `Blocked for your graphics driver version` appears in about:support. Lastly, the issue occurs in a clean Firefox profile, too, after some usage. Two relevant reports: https://www.reddit.com/r/firefox/comments/3gnmm6/hardware_acceleration_not_working_in_firefox_40/ https://www.reddit.com/r/firefox/comments/3gns6i/hardware_acceleration_became_disabled_in_firefox/
Also, screenshot of the current appearance of inbox.google.gom (the black horizontal lines): http://i.imgur.com/5CAtDrQ.jpg. And, I've also noticed high cpu usage with YouTube videos.
Component: General → Graphics
Product: Firefox → Core
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.