I'm sorry to hear about the troubles you're having. I've created a collection, where I will gather highlights showing the crashes occurring (so they don't get deleted by twitch after 30 days): Įcho -n "I am cpw on the lwjgl forums, I signed up on " | sha256sum This evening I dedicated an hour long stream to investigating this, with no real results. I'm happy to try building local copies with additional debugging enabled, but I am not familiar with the Memory code.įor a view of what's happening, I would recommend my recent twitch streams - it happens pretty frequently, usually accompanied by a bout of swearing. What I would like is guidance on how I can possibly debug this problem. Perhaps your reporting functions aren't durable to a JVM SEGV? Furthermore, no errors seem to be reported by any of the debugging I have enabled, and yet the error persists. It seems to me that the 1.13 update, with my rather wider scoped use of threading, seems to have caused LWJGL to overwrite parts of the stack somehow? I've read about the debugging of the new MemoryUtil functions, and turning on debugging seems to reduce the incidence of the issue somewhat - but it does not completely remove it. The computer I'm running on has passed all memtests I've thrown at it, and is quite capable of playing any other graphically intensive game going, including older versions of Minecraft, so although I initially thought "hardware (failing memory)" as the problem, I think I can safely discount that. I've encountered an actual "Stack smash" error on one occasion, numerous SEGV/SIGBUS and SEGV/SIGABRT errors, captured multiple core dumps (the only commonality is some REALLY weird thread traces in them), unmodifieable objects that are suddenly null, methods that fail with NPE at the end of the method (no functional code?!). For the past few weeks, I've been tackling the upgrade to 1.13 of Minecraft, and I am repeatedly encountering JVM aborts and game crashes, with a wide variety of different behaviours. I am cpw, one of the forge platform developers for Minecraft. It seems 99% likely to be an issue with LWJGL 3.1.6 at this point - I can't try newer because I'm tied to what the game is using. So this is quite the problem I seem to have.