User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0 Build ID: 20160604131506 Steps to reproduce: I actually don't know whether updating Firefox or Windows build caused it. But it has to be one of them, with the latter more probable. 1. Use Windows 10 build 14342. 2. Open Firefox and browse. 3. Wait for problem to occur. (I think watching YouTube made it faster to reproduce) Actual results: The window suddenly stopped repainting the UI and the webpage content. However, Firefox did not crash, moving the mouse still changed the cursor icon. Also, resizing the window does not trigger repainting. Expected results: Firefox should not stop repainting the window.

Also, regarding the image I attached, please notice some major points: - I resized the window, but Firefox didn't repaint, so the minimize, maximize and close buttons went out of canvas. - The bottom right is my insider build number. - I pressed F12 to trigger inspector to further show repainting problem, thus the bottom part is gray and white. Otherwise, the page should be fully black unless sometimes a video is playing.

Could you type about:support in the location bar and copy here the section "graphics". In addition, could you test with HWA disables (restart FF): http://support.mozilla.org/en-US/kb/forum-response-disable-hardware-acceleration

(In reply to Loic from comment #2) > Could you type about:support in the location bar and copy here the section > "graphics". > > In addition, could you test with HWA disables (restart FF): > http://support.mozilla.org/en-US/kb/forum-response-disable-hardware- > acceleration Graphics Adapter Description Intel(R) HD Graphics Adapter Drivers igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32 Adapter RAM Unknown Asynchronous Pan/Zoom none ClearType Parameters Gamma: 2200 Pixel Structure: R Device ID 0x0102 Direct2D Enabled true DirectWrite Enabled true (10.0.14342.1000) Driver Date 5-27-2015 Driver Version 9.17.10.4229 GPU #2 Active false GPU Accelerated Windows 1/1 Direct3D 11 (OMTC) Subsys ID 361617aa Supports Hardware H264 Decoding Yes Vendor ID 0x8086 WebGL Renderer Google Inc. -- ANGLE (Intel(R) HD Graphics Direct3D11 vs_4_1 ps_4_1) windowLayerManagerRemote true AzureCanvasAccelerated 0 AzureCanvasBackend direct2d 1.1 AzureContentBackend direct2d 1.1 AzureFallbackCanvasBackend cairo I will go disable my graphics acceleration now and will report back if I still get the problems. It will take a few hours. :)

You should update your drivers, they are of pre-Win 10 release.

(In reply to Loic from comment #4) > You should update your drivers, they are of pre-Win 10 release. I'm using a 4-year-old computer (since purchase) and Intel has stated not to provide drivers for old PCs in their new website and driver updating utility. So unless I can find or someone else tell me about a trusting place I can update my drivers, it's not going to update soon. :(

What's the model name of your intel CPU?

(In reply to Loic from comment #6) > What's the model name of your intel CPU? It seems OK now that I've turned off hardware acceleration. My intel CPU is Intel(R) Pentium(R) CPU G620 @ 2.60GHz, 2600 Mhz, 2 Core(s), 2 Logical Processor(s) (from system info) I didn't have my drivers rolled back when I updated to this Windows build and FF rendered fine before. I wonder, maybe this build changed some behavior??

There certainly are changes to Windows we've seen fix and introduce problems like this. When the problem happens, are the "bad" areas behaving like transparency in Firefox and showing the applications behind?

Also, when you have acceleration and the problem happens, does opening about:support work, and are there errors listed at the end of the graphics section?

(In reply to Milan Sreckovic [:milan] from comment #8) > There certainly are changes to Windows we've seen fix and introduce problems > like this. When the problem happens, are the "bad" areas behaving like > transparency in Firefox and showing the applications behind? Everything inside the webpage turns black and occasionally scrolling around will render a bit of the border of the website's content, not like transparency if I've seen it correct. The CSS of the FF's UI will not repaint but remains the final render before the problem. So scrolling on the tabs won't show and resizing the window won't move the frame buttons. All click events work even though the graphics aren't showing. So if you can guess the clicking areas, you can still use the interface. I have updated to another Windows build. I'll test again.

(In reply to Milan Sreckovic [:milan] from comment #9) > Also, when you have acceleration and the problem happens, does opening > about:support work, and are there errors listed at the end of the graphics > section? Here to report back a day later using Windows build 14366, the problem no longer occur on my PC as far as I've noticed in a day of browsing.

I'm getting this on Windows 10 x64 (x64 nightly build, e10s enabled), without the flash plugin enabled. Hardware acceleration is on, and I have the latest drivers for my AMD HD7790 GPU. Seems to happen more often with web video. Has happened without web video. Compositing Direct3D 11 Asynchronous Pan/Zoom wheel input enabled; touch input enabled WebGL Renderer Google Inc. -- ANGLE (AMD Radeon HD 7700 Series Direct3D11 vs_5_0 ps_5_0) Hardware H264 Decoding Yes; Using D3D11 API Direct2D true DirectWrite true (10.0.10586.0) GPU #1 Active Yes Description AMD Radeon HD 7700 Series Vendor ID 0x1002 Device ID 0x665c Driver Version 16.200.1025.0 Driver Date 6-2-2016 Drivers aticfx64 aticfx64 aticfx64 amdxc64 aticfx32 aticfx32 aticfx32 amdxc32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64 Subsys ID 04521043 RAM 1024 Diagnostics ClearType Parameters Gamma: 2.2 Pixel Structure: RGB ClearType Level: 50 Enhanced Contrast: 50 AzureCanvasAccelerated 0 AzureCanvasBackend direct2d 1.1 AzureContentBackend direct2d 1.1 AzureFallbackCanvasBackend cairo ClearType Parameters Gamma: 2.2 Pixel Structure: RGB ClearType Level: 50 Enhanced Contrast: 50

A number of these should be resolved in the (not yet released) 16.300.* drivers.

Good to know. Any idea of when they'll be released?

My particular black screen issues have ceased after I updated to the latest AMD Crimson drivers, 16.6.2. Other folks mileage might vary.

Drivers can be found at amd.com

16.6.2 seems to fix my black screen problems too.

As version 16.6.2 deals with this issue, chances are this and bug 1275524 are the same.

Bulk move of gfx-noted bugs without priority to P3 for tracking.

Can this be closed out now? Do we need to blocklist anything still?

Works for me because non-Firefox code fixed it (the driver)