VideoGameSmash12
Assigned
Reported
MC-211064
Loading in a TrueTypeFont with an out-of-bounds size crashes the game
Fixed
MC-210457
Setting the worldspawn to out-of-bounds coordinates with /setworldspawn crashes the game
Duplicate
MC-210408
/spawnpoint allows players to set their spawnpoint to out-of-bounds coordinates, which crashes the game when trying to respawn
Fixed
Comments
With multiple monitors, I wasn't able to reproduce this.
"Fixed"
Clearly it wasn't. Multiple users are reporting similar performance issues.
What is the memory usage in-game like when the game starts to lag?
If multiple different people are reporting terrible performance from the same thing (world generation), then I think there's something actually wrong with how the world generation was written.
Do me a favor and see what the memory usage is like when the lagspikes happen. Sounds like somebody wrote something extremely inefficient when working with world generation.
There are reports of a memory leak happening with world generation. If you can recreate this, could you give the memory usage when these FPS drops happen?
Sounds like a memory leak.
It may a duplicate of MC-197355, but it's still a bug that should have been remedied in 1.17, but it appears it wasn't.
This doesn't really seem like a bug, just the product of inefficient code. The world freezing is caused by the Server thread trying to save everything to disk, so everything kind of "freezes" for a bit while it saves everything.
@violine1101 I've noticed multiple reports from different people with the same characteristics. This seems to be a legitimate issue introduced in 1.18 (memory leak?).
Reminds me of one time when I witnessed my game disintegrate back in 2018. Eventually even the title screen was messed up.
You may have some luck with the latest.log file stored in the .minecraft folder.
It's probably the mod's fault, not the game's fault.
This issue also affects 1.16.5 as well.
Just confirmed this also affects 1.16.5.
This still crashes the game as of 1.16.4.
Right, I'm familiar with this exploit. The issue is only present in servers running Spigot and its forks, and it's a result of an invalid namespace provided in the enchantment command. You're better off reporting it to those folks.