Closed sk7725 closed 2 years ago
Erisfiregamer1
commented
3 years ago Seeing the error, I feel like maybe Betamindy wasn't the whole cause of it. EXCEPTION_ACCESS_VIOLATION sometimes happens with not enough RAM exceptions, might not be the case for Mindustry doe.
sk7725
commented
3 years ago Seeing the error, I feel like maybe Betamindy wasn't the whole cause of it. EXCEPTION_ACCESS_VIOLATION sometimes happens with not enough RAM exceptions, might not be the case for Mindustry doe.
yes, the error here is that Mindustry failed to write a crash report.
Anuken
commented
3 years ago This isn't even my code that's crashing, it's a Windows DLL that is somehow involved in the (well-known, well-tested) window library I'm using. The last ""fix"" for this was a random change in a completely unrelated native library, which I don't even use anymore.
Anuken
commented
3 years ago I've updated the Windows DLLs. Nothing actually changed, but the file size is different, probably due to the differing compilation environment.
This is unlikely to fix anything, but I have no other leads and I'm not going to be implementing any more "fixes" until someone has a better idea.
This version runs and exits fine on my Windows VM, so there's no way for me to debug anything locally.
Anuken
commented
2 years ago Reopening since I can reproduce this on a VM now, and it's apparently become a widespread issue. I still don't know the cause, but I can try randomly recompiling until something happens.
code-explorer786
commented
2 years ago most descriptive & explanatory bug report in Mindustry
# The crash happened outside the Java Virtual Machine in native code.
oh no
Erisfiregamer1
commented
2 years ago that sounds bad
Kieaer
commented
2 years ago This error was first encountered when remake version 4.0 again. It's a very old bug, but it's definitely problematic to always throw an error at the same code location.
https://github.com/Anuken/Mindustry/issues/2186 Look this. same error
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J 3462 arc.backend.sdl.jni.SDL.SDL_GL_SwapWindow(J)V (0 bytes) @ 0x0000000002e23a01 [0x0000000002e239c0+0x41]
j arc.backend.sdl.SdlApplication.loop()V+271
j arc.backend.sdl.SdlApplication.(Larc/ApplicationListener;Larc/backend/sdl/SdlConfig;)V+204
j mindustry.desktop.DesktopLauncher.main([Ljava/lang/String;)V+22
v ~StubRoutines::call_stuband this issue code is
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j arc.backend.sdl.jni.SDL.SDL_Quit()V+0
j arc.backend.sdl.SdlApplication.cleanup()V+20
j arc.backend.sdl.SdlApplication.<init>(Larc/ApplicationListener;Larc/backend/sdl/SdlConfig;)V+181
j mindustry.desktop.DesktopLauncher.main([Ljava/lang/String;)V+23
v ~StubRoutines::call_stubI think it started after changing the chat feature to the IME function in the OS. because it has never been like this when using an image font file.
nuemu1005
commented
2 years ago I'm trying to enter the mindustry.ddns.net server in mindstry, but I can't because of an error
Kieaer
commented
2 years ago My idea is to run SQL_Quit after SDL_DestroyWindow with some delay.
It's hard to find the same problem in Java, but it's common in other languages.
Kieaer
commented
2 years ago 
I opened the data folder, the same error occurred for a long time.
Let's run this program with administrator privileges for a few months.
Anuken
commented
2 years ago I can no longer reproduce this problem with the latest BE / custom build.
For some inexplicable reason, builds from around July clearly demonstrate this issue, with the JVM crashing on every quit.
The latest version does not do this at all. I have no idea why. I did not change any native code. This makes absolutely no sense, but it's gone now.
Judging by @Kieaer's file modification timestamps, there have been no crashes in recent versions either; the latest one looks to be around July, nothing near the end of August.
Kieaer
commented
2 years ago I also don't get the error reproduced anymore. This seems to be a JVM or Windows DLL issue.
3952
Platform: Windows
Build: 21112
Issue: Crashes without a crash log. The reason turned out to be an old Betamindy jar that was hanging out in the BE folders, but still it should have given me a crash log.
Steps to reproduce: same as #3952
Link(s) to mod(s) used: sk7725/BetaMindy, although the outdated one that was not compatible with the current Mindustry, let alone 7.0
Save file: i didn't even get to open a map
If you remove the line above without reading it properly and understanding what it means, I will reap your soul. Even if you're playing on someone's server, you can still save the game to a slot.
(Crash) logs: here's the error.pid
Place an X (no spaces) between the brackets to confirm that you have read the line below.