Skip to content

Ensure that cryptographic objects are GC-untracked first #155833

Open

Description

@picnixz

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

Activity

  1. self-assigned this
    on Aug 15, 2026
  2. added a commit that references this issue on Aug 15, 2026
  3. added 2 commits that reference this issue on Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

extension-modulesC modules in the Modules dirtype-bugAn unexpected behavior, bug, or error

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions