Skip to content

Why does PyTorch3d not release the GIL? #2019

Description

@mhidalgo-rai

I hit this on a kNN run taking ages on CPU and blocking other C extensions from reacquiring the GIL. Is there any reason for this to be the case? Is at::Tensor ownership compromised if the GIL is released?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions