Furia Memory

What's New

Furia Memory — Changelog

1.1.0 — Manual Control Update

Added

   * /furiamemory snapshot — Captures the current heap usage, deduplication counters, active vertex lookup entries, and the lifetime peak of the vertex lookup. (Works in Servers and Singleplayer)    * Delta Diagnostics — Provides a secondary snapshot report showing changes in heap usage and vertex-cache activity between snapshots. (Works in Servers and Singleplayer)    * /furiamemory clean gc — Safely releases Furia-owned caches and explicitly requests a single garbage collection cycle. (Works in Servers and Singleplayer)

Changed

   * End of Automatic Memory Release — Memory and cache release is no longer automatic (important note: in older versions, this process was automatic instead of manual). Cleanup is now fully manual and can only be triggered through mod commands or performed naturally by the JVM at termination. This prevents sudden performance drops, stutters, and unexpected freezes during gameplay. (Works in Servers and Singleplayer)    * Targeted Cache Release — /furiamemory clean now releases only Furia-owned lookup structures without invoking blocking calls such as System.gc() or deliberately pausing the main game thread. (Works in Servers and Singleplayer)    * Operator Permissions — Cleanup commands on multiplayer servers now require Operator Level 2, ensuring that only authorized administrators can perform manual cleanup. (Server-exclusive)    * Transparent Metrics — Cleanup feedback now reports the exact number of released vertex lookup entries instead of estimating or claiming an unverified amount of freed RAM. (Works in Servers and Singleplayer)    * Peak Diagnostics — The vertex lookup system now tracks and displays its peak entry count, providing more accurate information for memory and cache diagnostics. (Works in Servers and Singleplayer)

Fixed

   * Sublist Guard — Fixed an issue where a non-positive namespace report limit could cause an invalid sublist exception.    * Accurate Cooldown Messaging — Fixed the cleanup cooldown message incorrectly reporting that zero memory had been freed. The command now displays the correct remaining cooldown time.

Recommended JVM Arguments

These arguments are optional and may help the Java Virtual Machine manage memory more efficiently alongside Furia Memory.

For Singleplayer/Client or Server startup arguments:

-XX:+UseG1GC  
\-XX:+UseStringDeduplication  
\-XX:MaxHeapFreeRatio=30  
\-XX:MinHeapFreeRatio=10  
\-XX:G1PeriodicGCInterval=60000

These arguments are completely optional — Furia Memory works normally without them.