Possible memory leak in Crafty 4.7.0 – server RAM not released after stop

Since updating to Crafty version 4.7.0, I am experiencing what appears to be a memory leak or improper memory cleanup when stopping a server.

When I stop or close a server from the Crafty panel, the server process does not fully release the allocated RAM. The memory remains occupied even though the server is shown as stopped in the panel.

As a result:

• The server remains loaded in RAM
• Starting the server again increases RAM usage further
• The only way to fully free the memory is to manually kill the process
• I have to do this every time, otherwise the server stays in memory indefinitely

Expected behavior:
When a server is stopped, all associated processes should terminate properly, and the RAM should be released automatically by the system.

Actual behavior:
RAM remains allocated after stopping the server, requiring a manual kill process to fully clean it up.

Steps to reproduce:

1. Start a server in Crafty 4.7.0
2. Stop the server using the Crafty panel
3. Check RAM usage
4. Observe that the memory is not released
5. Kill the server process manually → RAM is freed

Environment:

• Crafty version: 4.7.0
• OS: Linux (Debian 13)
• Server type: NeoForge (ATM10)

Additional notes:
This behavior did not occur (or was much less noticeable) in previous versions. It looks like the server process is not being fully terminated or some references remain active after shutdown.