debug memory leak

gistfile1.txt

 
Member
SuperQ commented on 23 Jul 2018 • 
One additional debugging option, get a dump of the goroutines with http://localhost:9100/debug/pprof/goroutine?debug=1. Normally it would be only a few, like this.

@juliusv
 
Member
juliusv commented on 23 Jul 2018
@SuperQ Yeah, I would recommend listing the active goroutines, as we already know it's connected to a goroutine leak. But prefer debug=2 over debug=1, so: http://localhost:9100/debug/pprof/goroutine?debug=2

@SpeedBlack
 
Author
SpeedBlack commented on 24 Jul 2018 • 
Hi,

I can't execute the command with debug=2 option :

# go tool pprof -svg http://xxxxx:9100/debug/pprof/goroutine?debug=2 > dump_goroutine_2.svg
Fetching profile over HTTP from http://xxxxx:9100/debug/pprof/goroutine?debug=2
http://xxxxx:9100/debug/pprof/goroutine?debug=2: parsing profile: unrecognized profile format
failed to fetch any profiles
Do you have any idea?

For the moment, please, find attachment dump of the goroutines (debug=1 option) and new pprof sample heap for node-exporter.
dumps.zip

For information, currently, the pod node-exporter uses 137MiB

Thanks,
Best regards.

@SuperQ
 
Member
SuperQ commented on 24 Jul 2018
The goroutine link doesn't require pprof, just curl. It's just a big text dump, not svg.

@SpeedBlack
 
Author
SpeedBlack commented on 24 Jul 2018 • 
Ok, thanks for the clarification.

Please, find attachment dump of the goroutines (debug=1 & debug=2).
goroutine_dump.zip

Thanks,
Best regards.