Skip to content

wiki: update Memory Allocator Trace documentation#83

Open
kovan wants to merge 1 commit intogolang:masterfrom
kovan:fix-allocfreetrace-docs
Open

wiki: update Memory Allocator Trace documentation#83
kovan wants to merge 1 commit intogolang:masterfrom
kovan:fix-allocfreetrace-docs

Conversation

@kovan
Copy link

@kovan kovan commented Feb 3, 2026

The GODEBUG=allocfreetrace=1 option was removed in Go 1.23.
Update the documentation to reflect current alternatives:

  • Memory profiling with -memprofile and -memprofilerate=1
  • GODEBUG=traceallocfree=1 with execution traces for advanced use

Also update the note about combining GODEBUG options to remove
the obsolete allocfreetrace reference.

Updates golang/go#75183

The GODEBUG=allocfreetrace=1 option was removed in Go 1.23.
Update the documentation to reflect current alternatives:

- Memory profiling with -memprofile and -memprofilerate=1
- GODEBUG=traceallocfree=1 with execution traces for advanced use

Also update the note about combining GODEBUG options to remove
the obsolete allocfreetrace reference.

Updates golang/go#75183
@gopherbot
Copy link

This PR (HEAD: cb7cd14) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/wiki/+/741460.

Important tips:

  • Don't comment on this PR. All discussion takes place in Gerrit.
  • You need a Gmail or other Google account to log in to Gerrit.
  • To change your code in response to feedback:
    • Push a new commit to the branch used by your GitHub PR.
    • A new "patch set" will then appear in Gerrit.
    • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
    • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
    • Multiple commits in the PR will be squashed by GerritBot.
  • The title and description of the GitHub PR are used to construct the final commit message.
    • Edit these as needed via the GitHub web interface (not via Gerrit or git).
    • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
  • See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants