Crash on Unstable (graphics)

Support and discussions for the x86/x64 Linux version of Pale Moon.

Moderator: trava90

User avatar
Lunokhod
Fanatic
Fanatic
Posts: 189
Joined: 2017-04-20, 21:25
Contact:

Re: Crash on Unstable (graphics)

Post by Lunokhod » 2020-01-18, 15:03

mach build picked up where it left off which was good. The GTK3 build is the same though (if I'm building it right of course, I changed this to gtk3)
ac_add_options --enable-default-toolkit=cairo-gtk3
Then I tried without gtk2/libmozgtk.so as suggested on another post. But if the option name is a descriptive one, there is no cairo in the earlier gdb bt. When I tried apitrace then apitrace replay, the first replay gave glarb5 shader missing messages, but then every subsequent replay of the same trace did not!
I found this:
https://bugzilla.mozilla.org/show_bug.cgi?id=1223810
and it also crashes on zooming out for me, but when I checked the patch was already applied.
If I file a bug against mesa, they would be much better able to see what is going wrong than me, so that seems a good next move to possibly get some useful suggestions.

User avatar
Lunokhod
Fanatic
Fanatic
Posts: 189
Joined: 2017-04-20, 21:25
Contact:

Re: Crash on Unstable (graphics)

Post by Lunokhod » 2020-01-20, 18:28

https://gitlab.freedesktop.org/mesa/mesa/issues/2378
I've found the same sort of problems on webgl, threejs and babylonjs content now. So I suppose it's a general webgl question.
I got a new error in an apitest replay from a babylonjs demo with layers acceleration disabled too:

Code: Select all

1075: message: shader compiler issue 1: type: 1, local: 0, shared: 0, gpr: 4, inst: 6, bytes: 32
1075: message: shader compiler issue 1: type: 0, local: 0, shared: 0, gpr: 4, inst: 21, bytes: 168
1180: message: major api error 2: GL_INVALID_OPERATION in glGetNamedBufferPointerv(non-existent buffer object 3857049061)
1180 @0 glDeleteBuffers(n = 1, buffers = &3857049061)
1180: warning: glGetError(glDeleteBuffers) = GL_INVALID_OPERATION
1738: message: shader compiler issue 1: type: 1, local: 0, shared: 0, gpr: 4, inst: 6, bytes: 32
1738: message: shader compiler issue 1: type: 0, local: 0, shared: 0, gpr: 4, inst: 21, bytes: 168
1947: message: shader compiler issue 1: type: 1, local: 0, shared: 0, gpr: 4, inst: 3, bytes: 16
25027: message: major shader compiler issue 3: 0:2(12): warning: extension `GL_ARB_gpu_shader5' unsupported in vertex shader
25027: message: major shader compiler issue 4: 0:2(12): warning: extension `GL_ARB_gpu_shader5' unsupported in fragment shader

User avatar
Lunokhod
Fanatic
Fanatic
Posts: 189
Joined: 2017-04-20, 21:25
Contact:

Re: Crash on Unstable (graphics)

Post by Lunokhod » 2020-01-24, 14:27

Chromium blocks all webgl on my laptop using nouveau. The slide-across page turning on Kaieteur News is provided by the website as a fallback for browsers that don't have webgl support enabled.
Blocking webgl can be reproduced in Pale Moon by either restarting in Safe Mode, or changing this pref to 'true' in about:config
webgl.disabled;true
That does not require a restart to take effect, so it's a good workaround if needed that can be done on the fly to mirror Chromium behaviour. Firefox is generally better with webgl content than Pale Moon at present with nouveau and old hardware, but even that's not perfect because on this babylonjs demo:
http://www.axeon.fr/CLIENT/AXEON_SOFTWARE/PARIS_Bastille/
it also drew a picture then froze, and locked up my OS.
The force-enabled settings are used to override GPU / driver blacklists because when proprietary driver support ends (if they are being used) there are no new updates, but they may still work OK. That's why they are separate to the regular enabled prefs.

Here's a fun webgl game that does work with nouveau, Pale Moon and my laptop btw :D
http://oos.moxiecode.com/js_webgl/xwing/

Post Reply