Even things as simple as: http://get.webgl.org/
Reverted back to 32.0.3 and WebGL works fine.
This here is exactly the reason why I suggested assembling some people with virtual machines with known clean Windows installations to test out Waterfox. This would help chase down bugs and implementation issues.
Problem is VM's don't do well with 3D content at all. And ones that do need expensive workstations, so not the best cost-effective way to do it. Posting these beta builds though seems to be helping though, as I'm pretty sure I know what the issue is, just testing it out now!
Did a fresh install of Waterfox 33.0.2 from the link above.
Made sure to delete all the files and folder that were still in the Waterfox program folder after I uninstalled WF 33.
Same crash as I had yesterday.
Verified that Firefox 33.0.2 does not crash on the same web page.
Crash happens as a web page is about to complete a progress bar box and then open the next page in their sequence.
Yes the build has resolved all the issues except the WebGL bug which I'm fixing right now.
33.0.3? Do you mean 32.0.3? That is that latest stable version you should be using. The builds we're talking about now are just for testing.
This calls WebGL in a different manner and probably isn't the best way. I think I know what the issue is though.
That's interesting and about:support gets information from the graphics drivers which are causing the issues.
Yes it's not, but working on it!
I must agree on that not being the right way to resolve the issue, but figured I would share all I found. I can't for the life of me find another article regarding 3 fixes for webgl and a java vulnerability that I wanted to ask if was included in this latest version of WF...will continue to hunt. I hope you resolve your issue ultimately.
It's not but I should have a working build out tomorrow if things go well. As for Java, if there are any vulnerabilities, it's Oracle's responsibility. Waterfox is up-to-date patch wise.
WebGL has always working with Waterfox, just sometimes test builds go awry!
You can still enable it! Just follow this guide for example.
I had to remove the UI option though because if a user had a language pack installed, they wouldn't have that UI element defined so they'd get an error and not be able to access about:preferences at all.
It is present in FF33. Has been present for a few versions now, you just have to enable it manually. I added the UI part to make it easier to enable but it caused the issues above unfortunately.
Edited by MrAlex - 10/31/14 at 1:08pm