Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/tools: please add heap dump viewer #45631

Open
chenk008 opened this issue Apr 19, 2021 · 1 comment
Open

x/tools: please add heap dump viewer #45631

chenk008 opened this issue Apr 19, 2021 · 1 comment

Comments

@chenk008
Copy link

@chenk008 chenk008 commented Apr 19, 2021

What version of Go are you using (go version)?

$ go version
go version go1.15.2 linux/amd64

What did you do?

My go program consume large memory. I want to know which type of object consumes a lot of memory.

I have tried pprof to analyze heap, it shows which method consumes a lot of memory. But a lot of goroutines have the same traceback that contains this method, each of these goroutines process different type object, I couldn't find which type of object consumes a lot of memory.

What did you expect to see?

A tool can be used to analyze heap dump

#16410

@ianlancetaylor ianlancetaylor changed the title Please add heap dump viewer x/tools: please add heap dump viewer Apr 19, 2021
@gopherbot gopherbot added this to the Unreleased milestone Apr 19, 2021
@ianlancetaylor ianlancetaylor modified the milestones: Unreleased, Unplanned Apr 19, 2021
@gudvinr
Copy link

@gudvinr gudvinr commented Apr 21, 2021

There is golang.org/x/debug/cmd/viewcore to view core dumps (can be dumped using gcore).

It is not the same and I kinda agree that WriteHeapDump can be helpful in some cases. But these dumps completely useless in current state since there's not a single tool that can produce human-readable information from heap dumps AFAIK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants