[BUG] Creative mode build tool Constructed mode placement doesn't perform garbage collection
Veylyn opened this issue ยท 3 comments
Is there an existing issue for this?
- I have searched the existing issues
Are you using the latest MineColonies Verison?
- I am running the latest alpha version of MineColonies for my Minecraft version.
Did you check on the Wiki? or ask on Discord?
- I checked the MineColonies Wiki and made sure my issue is not covered there. Or I was sent from discord to open an issue here.
Minecraft Version
1.19
MineColonies Version
1.0.1093-ALPHA
Structurize Version
1.0.459-ALPHA
Related Mods and their Versions
- Forge Version 43.1.47
- BlockUI Version 0.0.64-ALPHA
- Domum Ornamentum Version 1.0.67-ALPHA
Current Behavior
Loaded into a simple superflat world in creative to place a building using the constructed mode. Placing any building massively increases system side RAM usage in task manager, while allocated RAM in minecraft remains within expected usage. Effect is especially pronounced with large structures, and I have seen my RAM usage reach twice my memory allocation.
Memory usage before build tool used:
Memory usage after build tool used to place large schematic:
Memory usage on rebooting minecraft, loading same world, no change in viewing angle:
Expected Behavior
system should clean up memory after use. I am uncertain if this is simply a limitation of Java however.
Reproduction Steps
- Create a new creative mode world
- Check current task manager memory usage
- Place a large schematic through constructed mode
- View task manager memory usage. Usage has increased dramatically
- Reboot Minecraft. Memory usage is now much lower than after schematic placement
Logs
https://gist.github.com/Veylyn/86973b79d8d203ad1e7a0385952f7165
Anything else?
- Add a thumbs-up to the bug report if you are also affected. This helps the bug report become more visible to the team and doesn't clutter the comments.
- Add a comment if you have any insights or background information that isn't already part of the conversation.
That is how Java works: Java performs garbage collection itself, when memory gets full
When you say when memory gets full, do you mean when all available system memory gets full? Because this bug crashed my game despite having a good 20 GB of ram to spare