Did you check the WebGL prefs on the about:config page?

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

• http://kb.mozillazine.org/about:config

cor-el said

Did you check the WebGL prefs on the about:config page? You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

• http://kb.mozillazine.org/about:config

I know it my friend and I think everything is enabled. Check the screenshoots.

I’d suggest updating your graphics drivers. Also see the Upgrade your graphics drivers to use hardware acceleration and WebGL support article.

Tonnes said

I’d suggest updating your graphics drivers. Also see the Upgrade your graphics drivers to use hardware acceleration and WebGL support article.

I said in the first post, I have the LATEST drivers available for the R7 AMD Graphic card.

Here the picture, downloaded from this page:

http://support.amd.com/es-xl/download/desktop?os=Linux%20x86_64

If I downgrade to the version previous Quantium (56.x) everything works fine. Is in the 57.x versions the problem!!!!

I’d swear I saw a newer version that day but can’t find it right now.

Nevertheless, you might be suffering this or this bug, or another one related to WebGL on Linux.

Can you try opening about:config and setting security.sandbox.content.level to 0 (zero; default = 3) and have a look at these bugs, and report back your findings?

Helo. I've updated today to the last version, and I am getting more PROBLEMS now, even in my computer and another with Windows 10, AMD APU 9800 and the LASTEST graphic driver also. 16 GB in RAM, Asrock 350 PRo also.

First... With the opcion in 3, the radio.garden site open in and estrange way (you will see the picture) but after 5 seconds it crashed. But now, for the 90% of the web pages I am getting a BLACK page, is I move the mouse over the page sometime I am able to read something, or the web browser flick for seconds... GRRRR What is happening... (I am having this issue (black screen now in 3 different computer, linux, windows 7 and windows 10, all with ATI/AMD APU)

Now, using old Seamonkey for writting this repply... because I am unable to enter in support.mozilla.org without getting black screen after 2 or 3 seconds of opening...

Impossible for working now with the last update. just simple reading news.... impossible...

Here, another webpage I discovered in other computer. Ryzen 3 1200, motherboard Asrock 350 Pro4, 32 GB in RAM, Suse Leap, lastest drivers for the Radeon R7 240

Does it work if you disable that video driver or boot in safe mode?

Please follow steps given and provide feedback rather than adding new info about Firefox behavior, or you may not get any additional help. So:

- Did you read the entire support article given and try all steps? - Did you read the bugs and try the workaround?

Keep in mind you may still need to disable hardware acceleration regardless of updated drivers. You could also have a look here and at the bug it refers to. This could be a specific issue for Suse.

cor-el said

Does it work if you disable that video driver or boot in safe mode?

The video driver is in the kernel... "Difficult" to disabled it.!!!! Safe mode in linux only reduce the daemons procedure, and/or run in runlevel 3 (text mode, only console)

Tonnes said

Please follow steps given and provide feedback rather than adding new info about Firefox behavior, or you may not get any additional help. So: - Did you read the entire support article given and try all steps? - Did you read the bugs and try the workaround? Keep in mind you may still need to disable hardware acceleration regardless of updated drivers. You could also have a look here and at the bug it refers to. This could be a specific issue for Suse.

1.- Which one steps? In the post they are only a lot and lot text about problems.... I don't understand completely 2.- I read the bugs but I don't understand everything 3.- I tried with hardware acceleration ON and OFF in the web browser and the result is the same 4.- I have the latest drivers Linux and Windows 5.- I only want to use the firefox, I am not a programer, I don't know about computer languages, and the problems are not only in SuSE.

Running from command line, I got the following:

Error! Fail to load fglrx kernel module! Maybe you can switch to root user to load kernel module directly libGL error: open uki failed (Operation not permitted) libGL error: reverting to (slow) indirect rendering

This is when I try to open any webgl site

But listing my modules loades I got:

hgonzale@homero:~> lsmod | grep fglrx fglrx 15488421 161 amd_iommu_v2 18909 1 fglrx button 13971 1 fglrx

Then, the modulo fglrx is running (loaded)...

The firefox couldn't load the module, it has been made with the system.

For support articles, it’s always good to follow or check each step mentioned.

Did you try changing the sandbox parameter, so that you may be able to confirm the bugs mentioned?

However and given the message that acceleration is blocked by the platform in your info, the WebGL issue on Linux may be due to a bug - see this page on Reddit for more info, as well as related bugs like this one.

Also see this page. You can find more info about the (deprecated) fglrx support too.

You could fiddle with reverting some graphics settings to use skia instead of cairo, or use Firefox 52 ESR for WebGL testing purposes which should still support hardware acceleration in Linux.

You may also find this page interesting, as well as this page.

For Windows, are you sure this is a WebGL issue too, or just assuming? For that, I would create a new profile using about:config and launch Firefox to use that without changing or adding anything and see if the black screen issue persists, then disable hardware acceleration as a first (and only) step. Of course always remember to revert any setting that did not help/fix the issue, as well as to restart Firefox each time.

Tonnes said

For support articles, it’s always good to follow or check each step mentioned. Did you try changing the sandbox parameter, so that you may be able to confirm the bugs mentioned? However and given the message that acceleration is blocked by the platform in your info, the WebGL issue on Linux may be due to a bug - see this page on Reddit for more info, as well as related bugs like this one. Also see this page. You can find more info about the (deprecated) fglrx support too. You could fiddle with reverting some graphics settings to use skia instead of cairo, or use Firefox 52 ESR for WebGL testing purposes which should still support hardware acceleration in Linux. You may also find this page interesting, as well as this page. For Windows, are you sure this is a WebGL issue too, or just assuming? For that, I would create a new profile using about:config and launch Firefox to use that without changing or adding anything and see if the black screen issue persists, then disable hardware acceleration as a first (and only) step. Of course always remember to revert any setting that did not help/fix the issue, as well as to restart Firefox each time.

1.- I took screenshot about what is happening when changing the sandbox. I am able for run webgl page for 5 second and after crash. I submitted the report. Look the previous screenshots.

2.- bug? How can I solve it?

3.- On all previous Firefox before Quantum the WebGL was working perfectly, but I wanted to update it, and maybe I will need to comeback. Even, in Seamonkey is working perfectly

4.- In windows is NOT working. Doing it. The common are ATI/AMD graphic cards, AMD CPU and Asrock motherboars. APU 9800, APU 7890K (mine) and Ryzen.

Really. Going back to 52. Customers getting crazy with the Firefox (all with Linux) and sometime my X server is crashing when I have many tabs opens.. VERY BAD product...really!!!!!! Try it before putting for the customer. BAD experience!