Skip to content

runtime: memory allocated with settype should not show up in profiles #4850

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.

Sign up for GitHub

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

Jump to bottom
Closed
rsc opened this issue Feb 20, 2013 · 2 comments
Closed

runtime: memory allocated with settype should not show up in profiles #4850

rsc opened this issue Feb 20, 2013 · 2 comments
Labels
FrozenDueToAge
Milestone
Go1.1

Comments

@rsc
Copy link
Contributor

rsc commented Feb 20, 2013 

Memory allocated with settype is internal bookkeeping and should not show up in memory
profiles reported by pprof. Because it is amortized across many calls, charging it to
the call of the initial allocation is misleading and confusing. The fix should be fairly
easy. I think there is a "no profiling" flag bit already.
@rsc
Copy link
Contributor Author

rsc commented Mar 12, 2013

Comment 1:

Labels changed: added go1.1maybe, removed go1.1.

@dvyukov
Copy link
Member

dvyukov commented Mar 14, 2013

Comment 2:

This issue was closed by revision 76959e2.

Status changed to Fixed.

@rsc rsc added fixed labels Mar 14, 2013
@rsc rsc added this to the Go1.1 milestone Apr 14, 2015
@rsc rsc removed the go1.1maybe label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Go1.1
Development

No branches or pull requests
3 participants
@rsc @dvyukov @gopherbot