Minecraft freezes/freaks out with "context reset due to GPU hang"
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Exactly what the title says. I think it might be linked to memory or GPU usage, but I haven't found a way to reliably reproduce it yet. I was hoping someone who knows Voxy's code might have some better ideas as to what exactly the problem is?
I tried both XWayland GLFW and native Wayland GLFW, saw this problem happen with both.
Full logs: https://mclo.gs/OMXdj85
The glitch was happening between 15:46:52 and 15:51:17, nothing was logged
Video of me reproducing a freeze: https://youtu.be/WK4OjL0mCSE
Video of Minecraft freaking out: https://youtu.be/1p-h8QldQU4
System info:
Intel Core i7-1255U
Intel Iris Xe Graphics (Integrated)
Arch Linux x86_64
KDE Plasma 6.5.3
KWin (Wayland)
16 GB RAM + 24 GB swap partition
There's also a 50% chance that my entire computer has a massive lag spike when I switch away from/to Minecraft even when it's not doing the freezing thing, but I don't know if that's related to this or just my computer being slow.
Thank you!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the linked full logs around 15:46:52–15:51:17 and comparing the reported behavior under native Wayland and XWayland GLFW. Use the provided videos and Intel Iris Xe, Arch Linux, and KDE Wayland setup as reproduction context; the issue is done when the GPU hang can be reproduced reliably and its cause is fixed or clearly isolated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- arch-linux, java, linux
- Domain
- computer-graphics, operating-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100