cmd/pprof: heap command top and traces show different data #34236
Labels
FrozenDueToAge
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
go env
)?$ go env GOARCH="amd64" GOBIN="" GOCACHE="/data/tbase/.cache/go-build" GOEXE="" GOFLAGS="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOOS="linux" GOPATH="/data/tbase/oss_compile/golang_pkg/packages:" GOPROXY="" GORACE="" GOROOT="/usr/lib/golang" GOTMPDIR="" GOTOOLDIR="/usr/lib/golang/pkg/tool/linux_amd64" GCCGO="gccgo" CC="gcc" CXX="g++" CGO_ENABLED="1" GOMOD="" CGO_CFLAGS="-g -O2" CGO_CPPFLAGS="" CGO_CXXFLAGS="-g -O2" CGO_FFLAGS="-g -O2" CGO_LDFLAGS="-g -O2" PKG_CONFIG="pkg-config" GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build502356231=/tmp/go-build -gno-record-gcc-switches"
OutputWhat did you do?
I write a program to test pprof heap but I found someting inconsisitent.
What did you expect to see?
Top command shows nothing but traces command shows there are many memory usage.
And when I used top only to found out it did not cause that much memory.
Here is my program.
How can I explain their difference?
What did you see instead?
The text was updated successfully, but these errors were encountered: