-
-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
Memory leak in tracemalloc #121390
Labels
type-bug
An unexpected behavior, bug, or error
Comments
vstinner
pushed a commit
that referenced
this issue
Jul 5, 2024
The tracemalloc_tracebacks hash table has traceback keys and NULL values, but its destructors do not reflect this -- key_destroy_func is NULL while value_destroy_func is raw_free. Swap these to free the traceback keys instead.
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jul 5, 2024
…1391) The tracemalloc_tracebacks hash table has traceback keys and NULL values, but its destructors do not reflect this -- key_destroy_func is NULL while value_destroy_func is raw_free. Swap these to free the traceback keys instead. (cherry picked from commit db39bc4) Co-authored-by: Josh Brobst <jbrobst@proton.me>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jul 5, 2024
…1391) The tracemalloc_tracebacks hash table has traceback keys and NULL values, but its destructors do not reflect this -- key_destroy_func is NULL while value_destroy_func is raw_free. Swap these to free the traceback keys instead. (cherry picked from commit db39bc4) Co-authored-by: Josh Brobst <jbrobst@proton.me>
Fixed by db39bc4. |
vstinner
pushed a commit
that referenced
this issue
Jul 5, 2024
…#121393) gh-121390: tracemalloc: Fix tracebacks memory leak (GH-121391) The tracemalloc_tracebacks hash table has traceback keys and NULL values, but its destructors do not reflect this -- key_destroy_func is NULL while value_destroy_func is raw_free. Swap these to free the traceback keys instead. (cherry picked from commit db39bc4) Co-authored-by: Josh Brobst <jbrobst@proton.me>
noahbkim
pushed a commit
to hudson-trading/cpython
that referenced
this issue
Jul 11, 2024
The tracemalloc_tracebacks hash table has traceback keys and NULL values, but its destructors do not reflect this -- key_destroy_func is NULL while value_destroy_func is raw_free. Swap these to free the traceback keys instead.
estyxx
pushed a commit
to estyxx/cpython
that referenced
this issue
Jul 17, 2024
The tracemalloc_tracebacks hash table has traceback keys and NULL values, but its destructors do not reflect this -- key_destroy_func is NULL while value_destroy_func is raw_free. Swap these to free the traceback keys instead.
vstinner
pushed a commit
that referenced
this issue
Jul 21, 2024
…#121392) gh-121390: tracemalloc: Fix tracebacks memory leak (GH-121391) The tracemalloc_tracebacks hash table has traceback keys and NULL values, but its destructors do not reflect this -- key_destroy_func is NULL while value_destroy_func is raw_free. Swap these to free the traceback keys instead. (cherry picked from commit db39bc4) Co-authored-by: Josh Brobst <jbrobst@proton.me>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
Bug description:
The
tracemalloc_tracebacks
hash table has traceback keys and NULL values, but its destructors do not reflect this --key_destroy_func
is NULL whilevalue_destroy_func
israw_free
. The leaked traceback keys can be seen with AddressSanitizer:CPython versions tested on:
CPython main branch
Operating systems tested on:
Linux
Linked PRs
The text was updated successfully, but these errors were encountered: