-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
A possible resource leak in Python 3.11.0 #98872
Labels
type-bug
An unexpected behavior, bug, or error
Comments
@SQLPATCH |
SQLPATCH
added a commit
to SQLPATCH/cpython
that referenced
this issue
Nov 3, 2022
miss-islington
pushed a commit
that referenced
this issue
Nov 24, 2022
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Nov 24, 2022
…GH-99047) Issue: pythonGH-98872 (cherry picked from commit 4e5f2db) Co-authored-by: SQLPATCH <95843853+SQLPATCH@users.noreply.github.com> Automerge-Triggered-By: GH:kumaraditya303
miss-islington
added a commit
that referenced
this issue
Nov 24, 2022
Thanks for the bug report and PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
Hi, I'm currently using Infer, a static analysis tool, to analyze the native code of CPython.
I found a possible resource leak vulnerability:
Resource of type
_IO_FILE
acquired by call tofopen()
at line 184 is not released after line 196.Programs/_freeze_module.c:196:
I think that resource should be released before exiting, a PR maybe like:
Python is my favorite programming language. I hope this discovery can be helpful to you!
My environment
The text was updated successfully, but these errors were encountered: