OS and browser crashes and freezes with webgl, threejs and babylonjs using nouveau and Pale Moon
I first had problems when layers.acceleration.disabled was set to false in about:config on this page:
https://www.kaieteurnewsonline.com/
This post here on the Pale Moon forum discusses it:
https://forum.palemoon.org/viewtopic.php?f=37&t=23512
There is more hardware and system info available there, I'm using a Dell Precision M4400 with 8GB RAM, Intel Core2 Duo T9900, NVIDIA G96GLM [Quadro FX 770M] and Artix Linux. I have rebuilt Pale Moon and related packages with debug symbols and attach gdb back trace details and apitrace traces of various instances. The back traces are not always the same. Sometimes the browser window freezes, or it may crash and dump core file. Sometimes the whole OS locks up and the power button has to be pushed and held. Once an unkillable Pale Moon process was left and a reboot was required to get rid of it. I have found similar problems with threejs, webgl and babylonjs demos. babylonjs does not require layers acceleration to be enabled to cause problems, neither does the Fillory threejs demo although most of those will work like that. Another less powerful PC I tried briefly was even more problematic.
https://www.khronos.org/registry/webgl/sdk/demos/google/san-angeles/index.html
https://demos.littleworkshop.fr/infinitown
http://www.axeon.fr/CLIENT/AXEON_SOFTWARE/PARIS_Bastille/
Do you think this is something that mesa / nouveau might be able to improve on, or do you consider it a browser issue? If so, do you have any suggestions or advice that could help the Pale Moon developers? The apitrace replay messages possibly provide some hints but I've never used it before. The missing function messages are from unused functions included in a header.