Open EmZaid opened 3 months ago
I also sometimes get this crash on startup. When I tried to restart the game from Prism after the last crash it crashed while loading. Crash log from that is attached below. It appears to be the same exception access violation error.
hs_err_pid17784.log
This is weird. I'm still looking at what might be causing it. If you know of ways to get better logs let me know.
Your GTNH Discord Username
Liminal Emily
Your Pack Version
2.6.1
Your Server
private server
Java Version
Java 21
Type of Server
Open To LAN
Your Actions
As a note about the server. I am hosting my own server through hetzner. It has no gui, so I'm starting it on the cli. But the server is not what is crashing. Both the server and the client are using Java 21
The server is set up to use 6gbs of ram, and my home computer is set up to use 16gbs for minecraft through Prism.
Issue
I load into the world and the game crashes when I am looking around. Sometimes it happens when I open a chest, I can't seem to find a reason for this crash. I have been playing for about 100 hours and now I can't play for more then about 5 minutes without crashing. Just walking around seems to cause this issue. It crashes my client to desktop and I have to reload the game.
Changes made to pack
Steps I've taken
Next things I was planning on trying
hs_err_pid8044.log
I am also including the image from windows security and maintenance. In this it seems like the issue is with OpenAL.dll.
Below is also the fml-client-latest.log
fml-client-latest.log
Let me know if you need more information or have any ideas. I appreciate all of the hard work yall do on this pack.
Best,
LiminalEmily
As an aside, I was worried I was doing something wrong I played until I had another crash. I tried lowering some graphics settings and had a slightly longer play time, but it still crashed. Same conditions as above. Here are the logs from that crash: hs_err_pid17192.log It had the same Security and Maintenance log output pointing at OpenAl.dll again
Crash Report
First crash: hs_err_pid8044.log fml-client-latest.log
Second crash: hs_err_pid17192.log fml-client-latest.log
Final Checklist