Open
Conversation
Contributor
Author
Collaborator
|
I was not aware that 3x3 crafting was available in this version actually, interesting. |
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.

Description
Fixed a read access violation crash occurring during the fireworks crafting process due to unstable memory management in FireworksRecipe
Changes
Previous Behavior
The game would crash when trying to craft fireworks
Root Cause
The
FireworksRecipeused Thread Local Storage to temporarily store theresultItem. Because the crafting validation (matches()) and the actual item generation (assemble()) were called from different thread contexts, the TLS would return a nullptr. Attempting to callcopy()on this null pointer caused a read access violation.New Behavior
The game doesn't crash when crafting fireworks
Fix Implementation
resultItemto a private class memberresultItemto be a private member of theFireworksRecipeclass.AI Use Disclosure
No (I used AI to help debug the crash logs and refine the technical explanation, but the code logic was manually refactored).
Related Issues