Skip to content

[3.8] closes bpo-41533: Fix a potential memory leak when allocating a stack (GH-21847) #22015

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 1 commit into from
Sep 4, 2020

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Aug 30, 2020

Free the stack allocated in va_build_stack if do_mkstack fails
and the stack is not a small_stack
(cherry picked from commit 75c80b0)

Co-authored-by: Tony Solomonik tony.solomonik@gmail.com

https://bugs.python.org/issue41533

Automerge-Triggered-By: @Mariatta

…pythonGH-21847)

Free the stack allocated in va_build_stack if do_mkstack fails
and the stack is not a small_stack
(cherry picked from commit 75c80b0)

Co-authored-by: Tony Solomonik <tony.solomonik@gmail.com>
@miss-islington miss-islington merged commit 66e9c2a into python:3.8 Sep 4, 2020
@miss-islington miss-islington deleted the backport-75c80b0-3.8 branch September 4, 2020 22:26
@miss-islington
Copy link
Contributor Author

@tontinton and @benjaminp: Status check is done, and it's a success ✅ .

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.

6 participants