This PR fixes the remaining memory leak I promised to investigate.
Here, the basis of the issue was an inadvert unique misuse of index/slot 0 (worldspawn index) in a clients loop for a certain array list cell allocation, that was never freed in the paired de-allocation loop.
This may satisfy remaining involved leaks per #15.
This PR fixes the remaining memory leak I promised to investigate.
Here, the basis of the issue was an inadvert unique misuse of index/slot 0 (worldspawn index) in a clients loop for a certain array list cell allocation, that was never freed in the paired de-allocation loop.
This may satisfy remaining involved leaks per #15.