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.

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

[3.6] bpo-29564:_PyMem_DumpTraceback() suggests enabling tracemalloc (GH-10510) #10518

Merged
merged 1 commit into from
Nov 13, 2018
Merged

[3.6] bpo-29564:_PyMem_DumpTraceback() suggests enabling tracemalloc (GH-10510) #10518

merged 1 commit into from
Nov 13, 2018

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented Nov 13, 2018 •
edited by bedevere-bot
Loading

If tracemalloc is not tracing Python memory allocations,
_PyMem_DumpTraceback() now suggests to enable tracemalloc
to get the traceback where the memory block has been allocated.

https://bugs.python.org/issue29564

@vstinner
bpo-29564:_PyMem_DumpTraceback() suggests enabling tracemalloc (GH-10510
db39553 
)

If tracemalloc is not tracing Python memory allocations,
_PyMem_DumpTraceback() now suggests to enable tracemalloc
to get the traceback where the memory block has been allocated.
@vstinner vstinner merged commit ae88781 into python:3.6 Nov 13, 2018
@vstinner vstinner deleted the memdump_tracemalloc36 branch November 13, 2018 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
skip news
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@vstinner @the-knights-who-say-ni @bedevere-bot