Skip to content

gh-126076: Account for relocated objects in tracemalloc #126077

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

Merged
merged 8 commits into from
Nov 19, 2024

Conversation

pablogsal
Copy link
Member

@pablogsal pablogsal commented Oct 28, 2024

@pablogsal
Copy link
Member Author

CC @vstinner

Co-authored-by: Victor Stinner <vstinner@python.org>
Copy link
Member

@vstinner vstinner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. But I suggest adding parenthesis in the macro implementation to avoid macro pitfals.

@pablogsal
Copy link
Member Author

LGTM. But I suggest adding parenthesis in the macro implementation to avoid macro pitfals.

Will do

pablogsal and others added 2 commits October 29, 2024 15:59
Co-authored-by: Victor Stinner <vstinner@python.org>
Co-authored-by: Victor Stinner <vstinner@python.org>
Copy link
Member

@markshannon markshannon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you make sure that all calls to _PyReftracerTrack are directly before the relevant free, to make it easier to merge them when we fix #125790

@pablogsal
Copy link
Member Author

Can you make sure that all calls to _PyReftracerTrack are directly before the relevant free, to make it easier to merge them when we fix #125790

Yup!

Copy link
Member

@picnixz picnixz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(I would have suggested using uppercase names for the macro but it wouldn't be consistent with the rest of the macros so I gave up)

Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
@vstinner
Copy link
Member

What's the status of this issue?

@pablogsal
Copy link
Member Author

I just need to land it after checking that I have addressed everything (I was on vacation 😉)

Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
@pablogsal pablogsal added the needs backport to 3.13 bugs and security fixes label Nov 19, 2024
@pablogsal pablogsal enabled auto-merge (squash) November 19, 2024 10:10
@pablogsal pablogsal merged commit 30aeb00 into python:main Nov 19, 2024
41 checks passed
@pablogsal pablogsal deleted the gh-126076 branch November 19, 2024 10:35
@miss-islington-app
Copy link

Thanks @pablogsal for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13.
🐍🍒⛏🤖

@miss-islington-app
Copy link

Sorry, @pablogsal, I could not cleanly backport this to 3.13 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker 30aeb00d367d0cc9e5a7603371636cddea09f1c0 3.13

@bedevere-app
Copy link

bedevere-app bot commented Dec 11, 2024

GH-127823 is a backport of this pull request to the 3.13 branch.

@bedevere-app bedevere-app bot removed the needs backport to 3.13 bugs and security fixes label Dec 11, 2024
pablogsal added a commit to pablogsal/cpython that referenced this pull request Dec 11, 2024
…ythonGH-126077)

(cherry picked from commit 30aeb00)

Co-authored-by: Pablo Galindo Salgado <Pablogsal@gmail.com>
pablogsal added a commit that referenced this pull request Dec 11, 2024
ebonnal pushed a commit to ebonnal/cpython that referenced this pull request Jan 12, 2025
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.

4 participants