Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

[3.14] gh-140067: Fix memory leak in sub-interpreter creation (GH-140111)#140118

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

@kumaraditya303
Copy link
Contributor

@kumaraditya303kumaraditya303 commentedOct 14, 2025•
edited
Loading

Fix memory leak in sub-interpreter creation caused by overwriting of the previously used_malloced field. Now the pointer is stored in the first word of the memory block to avoid it being overwritten accidentally.

(cherry picked from commit59547a2)

ashm-devand others added2 commitsOctober 14, 2025 20:17
…ythonGH-140111)Fix memory leak in sub-interpreter creation caused by overwriting of the previously used `_malloced` field. Now the pointer is stored in the first word of the memory block to avoid it being overwritten accidentally.(cherry picked from commit59547a2)Co-authored-by: Shamil <ashm.tech@proton.me>Co-authored-by: Kumar Aditya <kumaraditya@python.org>
@kumaraditya303kumaraditya303 changed the title[3.14] gh-140067: Fix memory leak in sub-interpreter creation (GH-14…[3.14] gh-140067: Fix memory leak in sub-interpreter creation (GH-140111)Oct 14, 2025
@kumaraditya303
Copy link
ContributorAuthor

There's a somewhat surprising failing test on gil-enabled tsan CI, will investigate later marking draft for now

cc@ZeroIntensity

@kumaraditya303kumaraditya303 marked this pull request as draftOctober 14, 2025 16:35
@ZeroIntensity
Copy link
Member

I think that's a known failure.

@ZeroIntensity
Copy link
Member

Oh, nevermind,#140111 was what caused that known failure.

@kumaraditya303kumaraditya303 marked this pull request as ready for reviewOctober 18, 2025 11:07
@kumaraditya303kumaraditya303 added the 🔨 test-with-buildbotsTest PR w/ buildbots; report in status section labelOct 18, 2025
@bedevere-bot
Copy link

🤖 New build scheduled with the buildbot fleet by@kumaraditya303 for commit150ae29 🤖

Results will be shown at:

https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F140118%2Fmerge

If you want to schedule another build, you need to add the🔨 test-with-buildbots label again.

@bedevere-botbedevere-bot removed the 🔨 test-with-buildbotsTest PR w/ buildbots; report in status section labelOct 18, 2025
@kumaraditya303kumaraditya303 merged commit1d11627 intopython:3.14Oct 18, 2025
105 of 110 checks passed
@kumaraditya303kumaraditya303 deleted the backport-59547a2-3.14 branchOctober 18, 2025 14:12
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@ericsnowcurrentlyericsnowcurrentlyAwaiting requested review from ericsnowcurrentlyericsnowcurrently is a code owner

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@kumaraditya303@ZeroIntensity@bedevere-bot@ashm-dev
[8]ページ先頭
©2009-2025 Movatter.jp