TypeError: Cannot read properties of null (reading 'uniformSetters')
matej2005 opened this issue · 8 comments
Hi I installed new version of TurboWarp (v1.10.1)
When i want to load any project i get TypeError: Cannot read properties of null (reading 'uniformSetters')
When i click OK project loads but stage is white and except variables monitors there is nothing here.
So i switched to flatpak version (v1.10.1), after while i got same error.
My OS is Pop!_OS 22.04 LTS x86_6 debian.
(Debug info: Distribution release-linux-deb-x64, Electron 26.6.8, linux x64)
(Debug info: Distribution release-linux-tar.gz-x64, Electron 26.6.8, linux x64)
send the project file to me, either here or contact@turbowarp.org
send the project file to me, either here or contact@turbowarp.org
It happens with every project.
Update
Disabling the addon custom-zoom, previous error disappears.
But the white stage will remain, if I want to put the stage in fullscreen (even without a project) , a same error will appear.
TypeError: Cannot read properties of null (reading 'uniformSetters')
Component stack: in gw in Connect(gw) ...
When i build Turbowarp-desktop myself, everything works as it should.
it does look like the flatpak is just broken, will get that fixed
I think there might be a bug somewhere in the latest versions of the Linux graphics stack; if I force software rendering with flatpak run --env=LIBGL_ALWAYS_SOFTWARE=1 org.turbowarp.TurboWarp it works
the root cause is that the webgl program used for rendering fails to link even though both of the shaders inside compiled okay, and getProgramInfoLog returns an empty string. i have no idea where in the stack that happens, but it's below the code we have direct control over...
it looks like just upgrading Electron magically fixes this so that's what we'll do (git master already did this so that's probably why your own build works). thanks!
in https://github.com/TurboWarp/desktop/releases/tag/v1.11.0-beta.3 i am no longer able to reproduce this on my test machine (you couldn't reproduce either when you built from source, so it's not just my machine)
but again it's a graphics driver bug wayyy below what we have direct control over; might be more issues there