gc optimize （HXCPP_GC_BIG_BLOCKS） #3
Conversation
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
1 participant
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.
By modifying a built-in setting in the GC (HXCPP_GC_BIG_BLOCKS), the GC's behavior has been shifted from being more suitable for 32-bit scenarios to 64-bit, improving its overall smoothness. Additionally, the only notable change is that it is no longer limited by the number of memory blocks, meaning it can support an almost unlimited number of arrows. Unlike before, where approximately over 90,000 notes would cause out-of-memory (OOM) errors, this issue is now resolved.
Additionally, you can download the build with HXCPP_GC_BLOCKS enabled from here: https://github.com/HEIHUAa/CodenameEngine-HEIHUA/actions/runs/20912168366