I wasn’t able to reproduce the crash just making the window fullscreen, but I did run into a similar-looking crash when exiting the game. For reference, I filed internal bug number 4764568.
I’m having the same issue, but for me, I don’t need to enter fullscreen; it crashes as soon as I launch 1.8.9 Minecraft (lwjgl 2). Any Minecraft version running lwjgl 3 starts and runs fine but also crashes for me on exit (as mentioned here).
OS: Arch Linux x86_64
Kernel: 6.10.6-arch1-1
DE: KDE Plasma 6.1.4
WM: Wayland sddm 0.21.0
CPU: AMD Ryzen 9 3900X (24) @ 3.800GHz
GPU: NVIDIA GeForce RTX 2060 SUPER
Manufacturer: Micro-Star International Co., Ltd
Product Name: MS-7C02
I just discovered that setting the environment variable __GL_THREADED_OPTIMIZATIONS=0 (on the application level, not globally) fixes both the lwjgl2 startup crash and the lwjgl3 shutdown crash.
Hi, @amrits . Sorry for disturbing you. Maybe this clue may speed up resolving the issue?
__GL_THREADED_OPTIMIZATIONS makes the issue. Without it no crash.
@xericl Great find. This fixes the crashes that occur when toggling full-screen and when quitting the game for me. I use PrismLauncher an I’ve added the environment variable to my instance settings for a seamless experience. Thanks again. This is a perfect band-aid until this issue receives a proper fix.
I have a similar issue: I play Minecraft through PrismLauncher on Nobara and the game often crashes when I maximize or exit maximization (it is not systematic, it crashes seemingly randomly).
I am adding a comment because adding the __GL_THREADED_OPTIMIZATIONS=0 environment variable on the PrismLauncher instance did not fix my issue
OS: Nobara Linux 40 (a version of Fedora)
Kernel: 6.10.7-200.fsync.fc40.x86_64 (64-bit)
DE: KDE Plasma 6.1.4
WM: Wayland
CPU: Intel® Core™ i7-8750H CPU @ 2.20GHz
GPU: NVIDIA GeForce GTX 1050
I… don’t know what you mean… from what I know, environment variables aren’t bound to a folder, and it doesn’t even exist on my system. How would I “put a variable” in a folder?
Thanks for the explanation, I did this and rebooted but the game crashed as soon as I clicked the “maximize” button.
I even checked: the command echo $__GL_THREADED_OPTIMIZATIONS does return 0.
Having the variable in a folder like this might not work because I installed Prism with Flatpak, I’m still surprised that setting the variable in the prism instance doesn’t work either, since it’s probably why this feature of prism exists in the first place.
Regarding the fact that the launcher goes through Flatpak, I also tried to set the variable for the launcher through Flatseal, but it did not work either.
Also, don’t worry about time, our time zones are different anyway.