Hello termer! >: If I remember correctly, -d:useMalloc only works for ARC/ORC, so if you're not using those, it has no effect.
The reason I compare other GC's is to show the problem persists with them too. Arc/Orc ram consumption results was included in my first message. > : I've dealt with the same issue, thinking the program was leaking memory > everywhere when really it was just keeping it for itself. If you're ever > doing debugging with Valgrind or similar, using -d:useMalloc can help, but in > general it does also let you return memory to the OS. Sure, there is indeed no memory leaks at all. At least leaksan not reports anything. I like valgrind, but sometimes I'm too lazy to use it :) > : I tend to compile with it because I don't like Nim sucking up memory and > freeing it at weird times. I expected GC_fullCollect() will force collector to do it's tasks. But no.. The more strange for me, is that I call it right before program exits, also sharedRam were "freed" right before it.
