Any parsers exist for go 1.5 heap dumps?

[Jack]

Hi,

I'm trying to debug a memory leak.  While pprof can tell me where the memory was allocated, it cannot tell me who owns the pointer to the memory.  I think I will need to parse a heap dump.  Searching found https://groups.google.com/d/msg/golang-nuts/a9fzypWTtcE/ZJrZEMhUDWMJ where someone else had a similar problem with no help.  I'm hoping to see if I can volunteer to write a solution to this problem, but want to know if one exists first or any resources that currently exist.

I have found https://golang.org/pkg/runtime/debug/#WriteHeapDump and https://github.com/golang/go/wiki/heapdump14.  Is heapdump14 valid for 1.5?

I found https://github.com/randall77 but randall77's repository panics on WriteHeapDump data (I'm using go 1.5 and just changing the header isn't enough) and others have reported github issues without response.  A github search didn't turn up anything else promising.  Is there other code that can get me started?

[Ian Lance Taylor]

[ + khr ]

> --
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Keith Randall]

Sorry, the heap viewer has not received the love it needs of late.  I don't think anything significant has changed from 1.4 to 1.5, so the viewer should still work.  Just a change from 1.4 to 1.5 in the header.

The heap dump viewer should work on pure Go dumps.  I've received problem reports on Go/cgo mixed applications due to unparseable (by the simple dwarf reader in the code) dwarf entries.  I'd appreciate patches if you have the time to look into the failures.

[Jack L]

I'm unable to get a hello world program to work.  I've filed a but report at https://github.com/randall77/heapdump14/issues/3 

[happyf...@gmail.com]

I am also in same position. Did you find or wrote anything?