if you do something like
/spreadplayers ~ ~ 1 1000000 true @e[type=!player]an error occurs and the game crashes
expected outcome:
error appears in command chat saying "too big of number idiot make it smaller" or something like that
actual outcome:
the error appears but a second after the game crashes and you have to wait ~7 minutes just to get back onto the world (thats just my pc)
could somebody with more coding knowledge think of a fix please?
Seems to be semi-fixed in 22w18a. Doesn't crash, just lingers around for a very long amount of time.
It seems to be completely fixed in 1.20.2
Linked issues
is duplicated by 1
Attachments
Comments 21
Alright! I have 32 GB of RAM in my computer. I allocated 16GB of it to Minecraft and I was able to run the command in my comment above successfully. It still took some time, but it didn't crash the game. That command must just be very memory hungry since it needs to figure out how to spread all the entities evenly.
[media][media]
We do not have enough information to find the cause of this issue.
Please attach the crash report found in [minecraft/crash-reports/crash-<DATE>-client.txt|https://minecrafthopper.net/help/finding-minecraft-data-folder/] here.
If you cannot find a crash report, please attach the full launcher log found in [minecraft/launcher_log.txt|https://minecrafthopper.net/help/finding-minecraft-data-folder/].
This issue is being temporarily closed as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
@violine1101 a crash report wasn't created when the game crashed. I did get an error code though.
Process crashed with exit code -805306369
Here is what Reliability History says about the crash
[media]
Here is what event viewer says about the crash
[media]
This time it closed automatically with this error code.
[media][media]
Here is the launcher log
[media]
There is no crash report to be found; it just hangs and becomes permanently unresponsive; you have to force close it.
I wasn't able to get the crash with your command.
But using this command below caused the internal server to freeze and then the game would end up crashing due to running out of memory. I'm not sure if there is a memory leak here or if this command just requires so much memory. I only have 2Gb of RAM allocated to Minecraft right now which is the default.
Even having a reasonable number, like 1000 can cause the game to crash or nearly crash.