Created attachment 8620827 [details] firefox button glitch/HW.png User Agent: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Firefox/38.0 Build ID: 20150525141253 Steps to reproduce: After a while of large usage of the browser in my computer with HW turned on, Mozilla Firefox would start to go crazy on my computer and would throw browser glitches all over the place. This has NOT happened possibly before version 33 when I had hardware acceleration turned on before in my Firefox and it was working fine. Actual results: When I have Hardware Acceleration turned on, Firefox's buttons on the top right, and Back button on the top left would display lines and button glitches and it should not do that at all. The color around the button is slightly lighter on the theme that I have applied on my Firefox. Also another problem would be Mozilla Firefox blacking out and glitching. This would make web browsing on Mozilla Firefox to be impossible to do. There after, forcing me to restart the browser and start over again. Expected results: Mozilla Firefox was (and is supposed to be) behaving normally on my computer with hardware acceleration turned on until a certain version of Mozilla Firefox made Firefox behave erratically on my computer. I do not want to turn off Hardware Acceleration because then it would make web fonts look sharp, small, pixelated and not smooth which I do not like, and that using the YouTube HTML5 player would push my CPU. But, that happens only when I have hardware acceleration turned off in my Firefox.
And also before someone asks this, yes I already do have the latest version of my graphics driver installed on my laptop computer that is experiencing this problem. Yes, I tried to do an update with Device Manager on my graphics driver and it said that it was the latest. Date on this driver is: 04/10/2012 according to Device Manager. Name of the graphics on my computer is: Mobile Intel(R) 4 Express Chipset Family. About:Support on Firefox says Unknown on the Adapter RAM, don't know why though.
Could you type about:support and paste the section "graphics", please.
Component: Untriaged → Graphics
Product: Firefox → Core
Does this also happen with a clean profile  and without addons? I'm just wondering from the screenshot if the themes / addons are doing something. Thanks!  https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data?redirectlocale=en-US&redirectslug=Profiles
(In reply to Loic from comment #2) > Could you type about:support and paste the section "graphics", please. Hi Loic, As you requested, here is the graphics section of about:support with hardware acceleration turned on in this computer: Graphics Adapter Description Mobile Intel(R) 4 Series Express Chipset Family Adapter Drivers igdumdx32 igd10umd32 Adapter RAM Unknown ClearType Parameters Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 400 Device ID 0x2a42 Direct2D Enabled true DirectWrite Enabled true (6.2.9200.17292) Driver Date 10-4-2012 Driver Version 18.104.22.16869 GPU #2 Active false GPU Accelerated Windows 1/1 Direct3D 11 (OMTC) Subsys ID 00000000 Vendor ID 0x8086 WebGL Renderer Google Inc. -- ANGLE (Mobile Intel(R) 4 Series Express Chipset Family Direct3D9Ex vs_3_0 ps_3_0) windowLayerManagerRemote true AzureCanvasBackend direct2d 1.1 AzureContentBackend direct2d 1.1 AzureFallbackCanvasBackend cairo AzureSkiaAccelerated 0 Please tell me if you do notice anything unusual or if there is something wrong.
(In reply to Mason Chang [:mchang] from comment #3) > Does this also happen with a clean profile  and without addons? I'm just > wondering from the screenshot if the themes / addons are doing something. > Thanks! > >  > https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-usest > data?redirectlocale=en-US&redirectslug=Profiles Hi Mason Chang, Yes, this also happens on a clean profile. I have done the "Refresh Firefox" feature before and this problem still occurs without anything on Firefox as well. I can still see the problem happen. (Hardware Acceleration turned on by default of course.)
You need to log in before you can comment on or make changes to this bug.