-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shader compilation broken #411
Comments
Thanks for the workaround! Element works fine after removing that file. |
In my case it was |
Same issue here, the fix works, Thank you |
even if i remove that folder, the issue exist. |
You need to restart the app |
Chromium finally fixed this, no idea, when it will show up in electron builds microsoft/vscode#190437 (comment) |
Would it make sense to drip the shader cache on startup of Element for now? It is supposed to be fixed in Chrome by now, but it'll take some time to "trickle down". |
Not sure, it might cause slowness, sucks either way. At least this MS person thinks it's no a good idea (but we're acting with a different slice of the userbase) |
I slower launching app for one instance is better than a non-working application. We could have it remove the cache only if the timestamp is too old or so. |
As far as I understand, this should be fixed now. At least in the case of element. Other electron apps might need to update their dependency. Vscode has also been fixed. |
After updating mesa element started and basically did not display anything usable.
See microsoft/vscode#190437 for the similar vscode issue
Can be fixed by running
The text was updated successfully, but these errors were encountered: