You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Hard JVM crashes when creating/loading worlds on Windows machines #487
cortex and I looked into this the other day, and there is potential that the 16 KiB stack allocation performed when transferring chunk sections to the natives is causing a stack overflow on memory-constrained Windows machines. i'll try to link all of the (potentially) related issues here. Could be something else too, but i think all of these errors are similar/related, or at least share the same failure mode.
changed the title [-]Mysterious JVM crashes when creating/loading worlds on low-memory Windows machines[/-][+]Hard JVM crashes when creating/loading worlds on low-memory Windows machines[/+]on Apr 25, 2026
changed the title [-]Hard JVM crashes when creating/loading worlds on low-memory Windows machines[/-][+]Hard JVM crashes when creating/loading worlds on memory-constrained Windows machines[/+]on Apr 25, 2026
Bumping this. Granted my system has 16gb total so I could try allocating more and seeing if it launches. By default I have ATLauncher give most modpacks 6gb and manually up this on heavier packs.
changed the title [-]Hard JVM crashes when creating/loading worlds on memory-constrained Windows machines[/-][+]Hard JVM crashes when creating/loading worlds on Windows machines[/+]on May 1, 2026
gemini told me to debug the minecraft process and I actually got something related to sable physics rope loading (I think. I may be wrong, I dont know anything about debugging I just wanna now why this crashes without a log): ModLoad: 00007ffe58f00000 00007ffe59086000 C:\Users*\AppData\Roaming\ModrinthApp\profiles\NeoForge 1.21.1.sable\natives\sable_rapier_x86_64_windows.dll
(934.6ec): C++ EH exception - code e06d7363 (first chance)
(934.6ec): Security check failure or stack buffer overrun - code c0000409 (!!! second chance !!!)
Subcode: 0x7 FAST_FAIL_FATAL_APP_EXIT
DBGHELP: https://msdl.microsoft.com/download/symbols is not a valid store
*** WARNING: Unable to verify checksum for C:\Users*\AppData\Roaming\ModrinthApp\profiles\NeoForge 1.21.1.sable\natives\sable_rapier_x86_64_windows.dll
sable_rapier_x86_64_windows!Java_dev_ryanhcode_sable_physics_impl_rapier_Rapier3D_wakeUpRope+0x1046e4:
00007ffe`5901ab34 cd29 int 29h
I been having the same issue, crashing when joining a world without anything in the logs. I was able to fix it by leaving my launcher open. Might help others avoid crashing idk, but whenever I got into my world my logs were flooded with
"[Render thread/ERROR] [de.ry.sa.Sable/]: Aborting entity get for abnormally large AABB: AABB[-300000.0, -300.0, -300000.0] -> [300000.0, 320.0, 300000.0]".
As soon as I close my launcher it would instantly crash when joining the same world, with the last thing in my log always being
[Server thread/INFO] [dev.ryanhcode.sable.Sable/]: Assigned physics scene ID 21 to minecraft:overworld
I been having the same issue, crashing when joining a world without anything in the logs. I was able to fix it by leaving my launcher open. Might help others avoid crashing idk, but whenever I got into my world my logs were flooded with "[Render thread/ERROR] [de.ry.sa.Sable/]: Aborting entity get for abnormally large AABB: AABB[-300000.0, -300.0, -300000.0] -> [300000.0, 320.0, 300000.0]".
As soon as I close my launcher it would instantly crash when joining the same world, with the last thing in my log always being [Server thread/INFO] [dev.ryanhcode.sable.Sable/]: Assigned physics scene ID 21 to minecraft:overworld
This is not what happened to me. I tried keeping my launcher open and it still crashed. Also, what do you mean by Assigned physics scene ID 21 to minecraft:overworld? For me it was ID 0 to minecraft:overworld. Not 21 , Specifically 0. Also, there was nothing about a windows message saying some features of the app were blocked.
I been having the same issue, crashing when joining a world without anything in the logs. I was able to fix it by leaving my launcher open. Might help others avoid crashing idk, but whenever I got into my world my logs were flooded with "[Render thread/ERROR] [de.ry.sa.Sable/]: Aborting entity get for abnormally large AABB: AABB[-300000.0, -300.0, -300000.0] -> [300000.0, 320.0, 300000.0]".
As soon as I close my launcher it would instantly crash when joining the same world, with the last thing in my log always being [Server thread/INFO] [dev.ryanhcode.sable.Sable/]: Assigned physics scene ID 21 to minecraft:overworld
This is not what happened to me. I tried keeping my launcher open and it still crashed. Also, what do you mean by Assigned physics scene ID 21 to minecraft:overworld? For me it was ID 0 to minecraft:overworld. Not 21 , Specifically 0. Also, there was nothing about a windows message saying some features of the app were blocked.
My scene ID is also 0. I don't know if this number is significant though.
I been having the same issue, crashing when joining a world without anything in the logs. I was able to fix it by leaving my launcher open. Might help others avoid crashing idk, but whenever I got into my world my logs were flooded with "[Render thread/ERROR] [de.ry.sa.Sable/]: Aborting entity get for abnormally large AABB: AABB[-300000.0, -300.0, -300000.0] -> [300000.0, 320.0, 300000.0]".
As soon as I close my launcher it would instantly crash when joining the same world, with the last thing in my log always being [Server thread/INFO] [dev.ryanhcode.sable.Sable/]: Assigned physics scene ID 21 to minecraft:overworld
This is not what happened to me. I tried keeping my launcher open and it still crashed. Also, what do you mean by Assigned physics scene ID 21 to minecraft:overworld? For me it was ID 0 to minecraft:overworld. Not 21 , Specifically 0. Also, there was nothing about a windows message saying some features of the app were blocked.
I also has 0 on other worlds but this time it was 21, the number might not be important. I use the FTB Launcher, and it seems to help it, I tried it on MultiMC and still kept crashing with launcher open. I also don't get any messages about Windows Defender and checking through the Windows Defender it didn't close it. I doubt this specific issue is related to Windows Defender.
@Random-Scientist you closed this as duplicate of #206, but that by definition cannot be correct, the issue of your post here is not because of Windows' smart app control blocking sable.
There's a really simple explanation: this consistently happens to people, including in your very own post here where you linked to some of these (like #274, #320), and consistent reports I've seen elsewhere, where it happens on Windows 10.
Windows 10 does not have Smart App Control, so I fail to see how it'd be the cause blocking Sable on Windows 10 machines (see e.g. https://support.microsoft.com/en-us/windows/app-browser-control-in-the-windows-security-app-8f68fb65-ebb4-3cfb-4bd7-ef0f376f3dc3). There's also no popup, notification (even in history), event viewer, 3rd party AV notification, quarantine report, or anything similar, on these scenarios. The issues might be in some way linked, but until that's completely verified, I think closing a possibly very different root cause of this issue that makes a lot of people be unable to use this mod be counter productive to finding a solution for it.
I'm also seeing plenty of these reports that end at [dev.ryanhcode.sable.Sable/]: Assigned physics scene ID 0 to minecraft:overworld and they have 12/16/24/32GB+ of RAM. See for example:
FTB Evolution crashed without a crash report. The logs have been uploaded to gnomebot.dev:
Activity
[-]Mysterious JVM crashes when creating/loading worlds on low-memory Windows machines[/-][+]Hard JVM crashes when creating/loading worlds on low-memory Windows machines[/+][-]Hard JVM crashes when creating/loading worlds on low-memory Windows machines[/-][+]Hard JVM crashes when creating/loading worlds on memory-constrained Windows machines[/+]ADaVinci22 commentedon Apr 27, 2026
@ryanhcode , I am experiencing the same issue, #320 is the one I uploaded, and I can't play with the mod unless you fix this bug
ryanhcode commentedon Apr 27, 2026
Concerning, hard to know if it's due to the chunk data uploads without any debug information / anybody able to run it in dev
Coach-mdl commentedon May 1, 2026
Bumping this. Granted my system has 16gb total so I could try allocating more and seeing if it launches. By default I have ATLauncher give most modpacks 6gb and manually up this on heavier packs.
ADaVinci22 commentedon May 1, 2026
@ryanhcode Could you try to make a debug build I can run so we can hopefully figure this out?
[-]Hard JVM crashes when creating/loading worlds on memory-constrained Windows machines[/-][+]Hard JVM crashes when creating/loading worlds on Windows machines[/+]amsteve873-png commentedon May 3, 2026
gemini told me to debug the minecraft process and I actually got something related to sable physics rope loading (I think. I may be wrong, I dont know anything about debugging I just wanna now why this crashes without a log): ModLoad: 00007ffe
58f00000 00007ffe59086000 C:\Users*\AppData\Roaming\ModrinthApp\profiles\NeoForge 1.21.1.sable\natives\sable_rapier_x86_64_windows.dll(934.6ec): C++ EH exception - code e06d7363 (first chance)
(934.6ec): Security check failure or stack buffer overrun - code c0000409 (!!! second chance !!!)
Subcode: 0x7 FAST_FAIL_FATAL_APP_EXIT
DBGHELP: https://msdl.microsoft.com/download/symbols is not a valid store
*** WARNING: Unable to verify checksum for C:\Users*\AppData\Roaming\ModrinthApp\profiles\NeoForge 1.21.1.sable\natives\sable_rapier_x86_64_windows.dll
sable_rapier_x86_64_windows!Java_dev_ryanhcode_sable_physics_impl_rapier_Rapier3D_wakeUpRope+0x1046e4:
00007ffe`5901ab34 cd29 int 29h
ryanhcode commentedon May 3, 2026
wait that's interesting i'll look into it soon
BlueCarbide commentedon May 4, 2026
I been having the same issue, crashing when joining a world without anything in the logs. I was able to fix it by leaving my launcher open. Might help others avoid crashing idk, but whenever I got into my world my logs were flooded with
"[Render thread/ERROR] [de.ry.sa.Sable/]: Aborting entity get for abnormally large AABB: AABB[-300000.0, -300.0, -300000.0] -> [300000.0, 320.0, 300000.0]".
As soon as I close my launcher it would instantly crash when joining the same world, with the last thing in my log always being
[Server thread/INFO] [dev.ryanhcode.sable.Sable/]: Assigned physics scene ID 21 to minecraft:overworld
Random-Scientist commentedon May 5, 2026
I'm now fairly convinced this is a duplicate of #206, feel free to reopen if you find out it isn't.
ADaVinci22 commentedon May 7, 2026
This is not what happened to me. I tried keeping my launcher open and it still crashed. Also, what do you mean by
Assigned physics scene ID 21 to minecraft:overworld? For me it wasID 0 to minecraft:overworld. Not 21 , Specifically 0. Also, there was nothing about a windows message saying some features of the app were blocked.Coach-mdl commentedon May 7, 2026
My scene ID is also 0. I don't know if this number is significant though.
BlueCarbide commentedon May 8, 2026
I also has 0 on other worlds but this time it was 21, the number might not be important. I use the FTB Launcher, and it seems to help it, I tried it on MultiMC and still kept crashing with launcher open. I also don't get any messages about Windows Defender and checking through the Windows Defender it didn't close it. I doubt this specific issue is related to Windows Defender.
Appulcake commentedon May 16, 2026
@Random-Scientist you closed this as duplicate of #206, but that by definition cannot be correct, the issue of your post here is not because of Windows' smart app control blocking sable.
There's a really simple explanation: this consistently happens to people, including in your very own post here where you linked to some of these (like #274, #320), and consistent reports I've seen elsewhere, where it happens on Windows 10.
Windows 10 does not have Smart App Control, so I fail to see how it'd be the cause blocking Sable on Windows 10 machines (see e.g. https://support.microsoft.com/en-us/windows/app-browser-control-in-the-windows-security-app-8f68fb65-ebb4-3cfb-4bd7-ef0f376f3dc3). There's also no popup, notification (even in history), event viewer, 3rd party AV notification, quarantine report, or anything similar, on these scenarios. The issues might be in some way linked, but until that's completely verified, I think closing a possibly very different root cause of this issue that makes a lot of people be unable to use this mod be counter productive to finding a solution for it.
I'm also seeing plenty of these reports that end at
[dev.ryanhcode.sable.Sable/]: Assigned physics scene ID 0 to minecraft:overworldand they have 12/16/24/32GB+ of RAM. See for example:FTB Evolution crashed without a crash report. The logs have been uploaded to
gnomebot.dev:latest.log | debug.log head / tail (~32k lines) | CurseForge: stdout-logs.txt | KubeJS: client.log / server.log / startup.log | crash_assistant_app.log | win_event1778952033381.txt | modlist.txt
FTB Evolution crashed without a crash report. The logs have been uploaded to
gnomebot.dev:latest.log | debug.log head / tail (~35k lines) | atlauncher.log | KubeJS: client.log / server.log / startup.log | crash_assistant_app.log | modlist.txt
FTB Evolution crashed without a crash report. The logs have been uploaded to
gnomebot.dev:latest.log | debug.log head / tail (~52k lines) | ftb-app-electron.log | KubeJS: client.log / server.log / startup.log | crash_assistant_app.log | modlist.txt | win_event1778535734181.txt
Coach-mdl commentedon Jun 2, 2026
Is there anymore news on this? I haven't been able to play the mod since launch and I'm starting to fear I never will.