12:30 <FromGitter> <Dan-Do> In lib C binding, do I need to dispose/free the memory which is initialized in crystal?

12:32 <FromGitter> <Dan-Do> for example, C lib has a struct like this ⏎ ⏎ ```code paste, see link``` ⏎ ⏎ And a func like this `fun iwkv_val_dispose(kval : IwkvVal*)` [https://gitter.im/crystal-lang/crystal?at=619b8de842fc2863b2200d64]

12:33 <FromGitter> <Dan-Do> In crystal wrapper I have `key = Lib::IwkvVal.new(data: Slice(UInt64).new(1).to_unsafe, size: sizeof(UInt64), compound: 0_u64)`

12:34 <FromGitter> <Dan-Do> Do I need to call `Lib.iwkv_val_dispose(pointerof(key))` manually?

12:34 <FromGitter> <straight-shoota> You're not allocating any heap memory. The value is just put on the stack which vanishes as soon as the program leaves the scope.

12:35 <FromGitter> <straight-shoota> Whether you need to inform the library about disposing a value is a question for the library, not Crystal.

12:35 <FromGitter> <Dan-Do> Uhm, but I see the memory takes to 2GB when using `top` command to monitor my process

12:38 <FromGitter> <straight-shoota> Dunno where that's coming from. Certainly not from that initializer. That should put roughly 12 bytes on the stack (and allocate 4 on the heap for the slice, but that's managed by the GC)

12:41 <FromGitter> <Dan-Do> Is there any method to tell me about where does 2GB come from?

12:42 <FromGitter> <straight-shoota> `GC.stats` could help

12:43 <FromGitter> <Dan-Do> Thank you, I will try

14:26 <FromGitter> <Dan-Do> There are errors when doing dispose/free the memory manually. ⏎ `munmap_chunk(): invalid pointer` ⏎ `free(): invalid pointer`

14:39 <straight-shoota> You can't free a stack pointer

14:43 <FromGitter> <Dan-Do> Yes, I can only free a pointer which is allocated in C lib `out var`