Closed rasa-silva closed 2 years ago
Hi @rasa-silva, could you provide the method on how you determined that the program is leaking memory? I tried with the render
example and ran leaks [pid]
after the program has been running for a while but it doesn't seem to show much memory leak apart from 16 bytes of memory.
I just monitored it with htop
and "Activity Monitor" and the value keeps rising every second
Does it keep rising and not drop down for you? In my case, it seems to stabilize around 30-40mb. It looks to me that it’s normal allocations and Go’s garbage collection running.
It seems you're right. It slowly rises during ~5 minutes but it stabilizes after that. Probably the Go runtime warming up or something like that... Sorry for the trouble. You can close this.
I see. If you experience severe memory leaks, do let me know and feel free to reopen this!
Running any example with a
Renderer
like render seems to leak memory. (at least on OSX)