12-08-2015, 02:29 AM
I'm not sure if it's a hard memory leak. I tried running Cuberite with valgrind for some time and after stopping, all the memory was properly freed.
It could still be a soft leak - the server knows about all the memory it allocated, but keeps allocating more and more.
I have no idea if there are any tools for Linux / BSD that could do live memory analysis. We're using a StackWalker for Windows builds that can keep track of each memory block's stacktrace at the time of allocation, so we could do some statistics on that (the dumpmem console command). This slows down everything so much that it's disabled by default and you'd need to set some preprocessor defines in order to enable it.
It could still be a soft leak - the server knows about all the memory it allocated, but keeps allocating more and more.
I have no idea if there are any tools for Linux / BSD that could do live memory analysis. We're using a StackWalker for Windows builds that can keep track of each memory block's stacktrace at the time of allocation, so we could do some statistics on that (the dumpmem console command). This slows down everything so much that it's disabled by default and you'd need to set some preprocessor defines in order to enable it.