Skip to content

Leaked instances of DuckDBPyType since 2.0 #736

Closed

Description

@jakkes

What happens?

Since 2.0, our runtimes end with what looks like leaked instances of DuckDBPyType.

nanobind: leaked 27 instances!
 - leaked instance 0x64c7922f1c50 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922f1c10 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e85b0 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e86d0 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e85d0 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e8630 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e8610 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e8730 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922f1c70 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e87d0 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e8670 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e8690 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e8810 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922f1c30 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e8590 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e8770 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e87b0 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e85f0 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e86f0 of type "_duckdb._sqltypes.DuckDBPyType"
 - leaked instance 0x64c7922e8710 of type "_duckdb._sqltypes.DuckDBPyType"
 - ... skipped remainder
nanobind: leaked 6 types!
 - leaked type "_duckdb._sqltypes.DuckDBPyType"
 - leaked type "_duckdb.DuckDBPyConnection"
 - leaked type "FunctionNullHandling"
 - leaked type "PythonUDFType"
 - leaked type "ExplainType"
 - leaked type "PythonExceptionHandling"
nanobind: leaked 84 functions!
 - leaked function "extract_statements"
 - leaked function "__exit__"
 - leaked function "fetchdf"
 - leaked function "_statement_count"
 - leaked function "install_extension"
 - leaked function "array_type"
 - leaked function ""
 - leaked function "interrupt"
 - leaked function "_own_sources"
 - leaked function "torch"
 - ... skipped remainder
nanobind: this is likely caused by a reference counting issue in the binding code.
See https://nanobind.readthedocs.io/en/latest/refleaks.html

To Reproduce

It seems this is due to interaction with other libs, torch in particular, and typing.overload.

This is a pure Python reproducer

import ctypes

import duckdb

ctypes.pythonapi.Py_IncRef(ctypes.py_object(duckdb.DuckDBPyConnection))

Here is a more realistic scenario.

$ cat lib.py
import typing

import duckdb


class Wrapper:
    def __init__(self, con: duckdb.DuckDBPyConnection): ...


# typing.overload stores the function in typing._overload_registry, which is not
# released at shutdown once torch has been imported.
@typing.overload
def f(x: int) -> None: ...
$ cat repro_torch.py
"""duckdb + torch + a module with a typing.overload and a DuckDBPyConnection annotation."""
import torch  # noqa: F401

import lib  # noqa: F401

Running python repro_torch.py provides the same error message.

OS:

Ubuntu 26

DuckDB Version:

2.0

DuckDB Client:

Python

Hardware:

No response

Full Name:

Jakob Stigenberg

Affiliation:

Qubos Systematic

Did you include all relevant configuration (e.g., CPU architecture, Linux distribution) to reproduce the issue?

  • Yes, I have

Did you include all code required to reproduce the issue?

  • Yes, I have

Did you include all relevant data sets for reproducing the issue?

Not applicable - the reproduction does not require a data set

Activity

  1. transferred this issue fromduckdb/duckdbon Nov 4, 2026
  2. evertlammerts commented on Nov 8, 2026

    @evertlammerts
    Member

    This is a duplicate of #732, will be addressed soon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions