Description

picnixz

opened on Aug 15, 2026

Issue body actions

Bug report

Bug description:

MD5 and SHA* objects free their HACL* state before they are GC-untracked. In addition, I believe that MD5 and SHA* objects do NOT need to actually be GC-tracked because they do not contain anything other than a plain HACL* state pointer which is not a Python object (but that's a separate issue).

CPython versions tested on:

CPython main branch

Operating systems tested on:

No response

Linked PRs

• gh-155833: GC-untrack MD5/SHA* objects before freeing the HACL* state #155834
• [3.15] gh-155833: GC-untrack MD5/SHA* objects before freeing the HACL* state (GH-155834) #159789
• [3.14] gh-155833: GC-untrack MD5/SHA* objects before freeing the HACL* state (GH-155834) #159790

Activity

1. picnixz

   self-assigned this

   on Aug 15, 2026
2. picnixz

   added

   type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error

   extension-modulesC modules in the Modules dirC modules in the Modules dir

   on Aug 15, 2026
3. picnixz

   added a parent issue on Aug 15, 2026

   • Meta-issue for bugs in cryptographic extension modules #155438
4. picnixz

   added a commit that references this issue on Aug 15, 2026

   pythongh-155833: GC-untrack MD5/SHA* objects before freeing the HACL*…

   662f191
5. picnixz

   added 3 commits that reference this issue on Oct 19, 2026

   gh-155833: GC-untrack MD5/SHA* objects before freeing the HACL* state (…

   29fd3b8

   [3.14] gh-155833: GC-untrack MD5/SHA* objects before freeing the HACL…

   5d9a691

   [3.15] gh-155833: GC-untrack MD5/SHA* objects before freeing the HACL…

   7e102ec
6. picnixz

   closed this as completedon Oct 22, 2026

Issue actions