Fix crash caused by accessing registry too early - #887
Merged
Conversation
Thanks to Lumine!!!
Dreeam-qwq
force-pushed
the
fix/max-stack-size-cache-crash
branch
from
August 18, 2026 08:17
b18bd22 to
b6aa363
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Another crash related to class init sequence. Very beautiful! Very powerful!
Issue analysis
Some plugins/libs may use
Class.forNameto check classes (cloud command framework in this issue.).The plugin EasyArmorStands uses Paper's lifecycle API, and init the cloud framework at Paper's bootstrap stage (actually it's before Minecraft's bootstrap). So it triggers the max stack size cache logic to access a registry (maybe I guess) before the registries are initialized, and causes
ExceptionInInitializerErrorin the end.So I just rewrote thePatchedDataComponentMapconstructor forItemStack#EMPTY, skippeddetectMaxStackSizeChangeand to prevent adding more conditions indetectMaxStackSizeChange. If you have a better solution, let me know (Yes, now it's a better approach
Error