fix: Intermittent Forgified Fabric API creative inventory crash on Forge 1.20.1 - #81
Open
arnabnandy7 wants to merge 2 commits into
Open
Conversation
Signed-off-by: Arnab Nandy <arnab_nandy7@yahoo.com>
Signed-off-by: Arnab Nandy <arnab_nandy7@yahoo.com>
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.
Summary
Fixes an intermittent creative inventory crash when Clutter No More is used with Forgified Fabric API and Sinytra Connector on Minecraft 1.20.1 Forge.
Fixes #27
Root cause
Clutter No More extends
ItemStackequality so generated shape items and their parent items compare as equivalent.However,
ItemStackLinkedSet.TYPE_AND_TAGcontinued calculating hashes from the original item. This violated the required equality/hash contract:Forge uses this strategy in
MutableHashedLinkedMapwhen building creative inventory tabs. Depending on the map layout, Forgified Fabric API's iterator-removal pass could remove an unexpected entry and throw:The inconsistent map layout explains why the crash occurred intermittently.
Solution
Regression verification
The regression check recreates the previous broken hash strategy using actual registered item stacks.
Before
It verifies that shape and parent stacks compare equal while producing different hashes, then reproduces the reported:
from
MutableHashedLinkedMap.Iterator.remove().After
It verifies that:
Successful runtime output:
Validation
The development regression check was executed during a Forge 1.20.1 server launch.
The following builds pass:
Runtime verification: