Re: [go-nuts] Investigating suspected memory leak based on StackInUse or HeapSys stats

I've already checked process threads using ps command, and threads are not leaking. Still, it is more than possible that there are memory leaks within my Cgo code, or gstreamer as well (Which I'm running with Cgo as well) But before I'm starting to chase this path, I would like to be sure heapSys

Re: [go-nuts] Investigating suspected memory leak based on StackInUse or HeapSys stats

Are you certain your CGo code isn’t creating threads? > On Mar 26, 2022, at 1:10 PM, Shlomi Amit wrote: > > Yes. I already monitoring the runtime stat of number of go routines (Can be > seen in the screenshot as well) and it's not increasing. > > On Sat, Mar 26, 2022, 20:40 robert engels

Re: [go-nuts] Looked at using Go ... nil/SEGV really bothered me .. Go2 Proposal?

Stephan Lukits > On 25 Mar 2022, at 20:41, 'Michael Toy' via golang-nuts > wrote: > > The discussion is quite informative https://m.youtube.com/watch?v=ynoY2xz-F8s -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this g

Re: [go-nuts] Investigating suspected memory leak based on StackInUse or HeapSys stats

Yes. I already monitoring the runtime stat of number of go routines (Can be seen in the screenshot as well) and it's not increasing. On Sat, Mar 26, 2022, 20:40 robert engels wrote: > Are you certain the number of Go routines is not increasing - each Go > routine requires stack. See https://tpas

Re: [go-nuts] Investigating suspected memory leak based on StackInUse or HeapSys stats

Are you certain the number of Go routines is not increasing - each Go routine requires stack. See https://tpaschalis.github.io/goroutines-size/ > On Mar 24, 2022, at 3:18 PM, Shlomi Amit wrote: > > Hi. > > I’m trying to find a memory leak in my application. > I’ve added some runtime memory sta