-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
runtime: GODEBUG=allocfreetrace=1 not working as go1.19.2 in go1.23.0 #68885
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
Comments
gopherbot
added
the
compiler/runtime
Issues related to the Go compiler and/or runtime.
label
Aug 15, 2024
Then I tried the new api from "runtime.trace" and "golang.org/x/exp/trace". I can not get stacktrace of every alloc.
I can not get stacktrace of every alloc:
|
bronze1man
changed the title
runtime: GODEBUG=traceallocfree=1 not working as go1.19.2 in go1.23.0
runtime: GODEBUG=allocfreetrace=1 not working as go1.19.2 in go1.23.0
Aug 15, 2024
GODEBUG=allocfreetrace=1 is very good tool to make my code faster with less heap alloc. |
runtime: remove allocfreetrace: https://go-review.googlesource.com/c/go/+/583376 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Go version
go version go1.23.0 darwin/amd64
Output of
go env
in your module/workspace:What did you do?
my code
What did you see happen?
nothing, only "abc"
What did you expect to see?
a lot of stack of alloc place of my code like in ./tmp/2.log
The text was updated successfully, but these errors were encountered: