Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Segfault at interpreter exit when the duckdb module outlives shutdown outside sys.modules

Abierto
  • ¿Algo no está bien?
#638 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp, python
Área
backend

Línea de trabajo

Start by running the provided repro on Python 3.11, then inspect DuckDBPyConnection::default_connection and import_cache in src/duckdb_py/pyconnection.cpp and _clean_default_connection in src/duckdb_py/duckdb_python.cpp. Trace cleanup during interpreter shutdown when duckdb is absent from sys.modules; done means the repro exits successfully with status 0 while the module reference remains alive.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

What happens?

The process segfaults at interpreter exit (exit status -11 / 139) when the duckdb module object stays alive but is no longer registered in sys.modules at shutdown. Nothing is printed by -X faulthandler, so the crash appears to happen after interpreter finalization.

A common way to get into this state is a test that uses unittest.mock.patch.dict(sys.modules): DuckDB is imported for the first time inside the block, and leaving the block restores the old snapshot, which removes duckdb/_duckdb from sys.modules. Any remaining reference, such as a sqlalchemy.ext.compiler.compiles hook registered by duckdb_engine, keeps the module alive.

Likely cause: the process-global default connection and import cache (DuckDBPyConnection::default_connection / import_cache, src/duckdb_py/pyconnection.cpp around lines 70-72 in v1.5.2) are released only by DuckDBPyConnection::Cleanup(). That function runs only when the _clean_default_connection capsule is destroyed (src/duckdb_py/duckdb_python.cpp around lines 1154-1157 in v1.5.2; the nanobind capsule on main has the same design). The interpreter clears module dicts during shutdown only for modules that are still in sys.modules, so the capsule is never destroyed while Python is alive. The C++ statics are then destroyed at exit(), after the interpreter is gone.

A cleanup that does not depend on the module dict being cleared would avoid this, e.g. one registered with Python's atexit, or Py_AtExit.

To Reproduce
import gc
import sys
from unittest import mock

with mock.patch.dict(sys.modules):
    import duckdb  # duckdb/_duckdb are removed from sys.modules on exit

def holder():
    pass

holder.module = duckdb  # any surviving reference keeps the module alive
gc.freeze()
print("exiting", duckdb.__version__, flush=True)

$ python repro.py; echo $?
exiting 1.5.5
Segmentation fault
139

With the same reference but without the patch.dict block, the process exits with status 0. It also exits with status 0 if the module is freed before shutdown.

OS:

Linux x86_64 (Debian, kernel 6.1)

DuckDB Package Version:

1.5.2 and 1.5.5

Python Version:

3.11.15

Full Name / Affiliation

N/A

Did you include all relevant configuration to reproduce the issue?
  • Yes
Lenguaje dominante
Python
Estrellas
186
Forks
113
Merge medio
1 d 1 h
PR fusionados (30 d)
16

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de duckdb/duckdb-python

Todos los issues de duckdb/duckdb-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.