Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Thin mode: setting `Connection.call_timeout` after DPY-4011 crashes the interpreter (SIGSEGV / 0xC0000005)

Aperta
  • Qualcosa non va?
#619 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python
Ambito
database

Direzione di ricerca

Start with the call_timeout setter in oracledb/connection.py (around line 578 in 26.0.0, line 197 in 4.0.2) and the thin implementation it calls, since the traces stop there. Reproduce with the script in the issue, which needs a second account with ALTER SYSTEM to kill the session. Done when assigning call_timeout on a connection that is_healthy() reports as False raises DPY-1001 or is a no-op, with no segfault, and the behaviour matches ping() and rollback().

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

1. What versions are you using?
  • python-oracledb 26.0.0 and 4.0.2, thin mode (both crash)
  • Python 3.11.16 (main, Aug 14 2026) [Clang 22.1.3]
  • Linux-7.0.0-38-generic-x86_64-with-glibc2.43
  • Also seen on Windows (access violation 0xC0000005), python-oracledb 26.0.0 and 4.0.2
  • Oracle Database 19c Enterprise Edition 19.9, non-CDB
2. Is it an error or a hang or a crash?

A crash. The process dies with SIGSEGV (exit status 139) on Linux, or 0xC0000005 on Windows. No Python exception is raised.

3. What error(s) or behavior are you seeing?

The session is killed on the server. The next call raises DPY-4011 as expected, and is_healthy() returns False. Reading call_timeout still works. Assigning call_timeout (any value, including 0) then crashes the interpreter:

execute: DPY-4011: the database or network closed the connection
is_healthy: False
call_timeout: 0
Fatal Python error: Segmentation fault

Current thread 0x00007748c983b740 (most recent call first):
  File ".../site-packages/oracledb/connection.py", line 578 in call_timeout
  File "repro.py", line 27 in <module>

Extension modules: oracledb.arrow_impl, oracledb.base_impl, oracledb.thick_impl, _cffi_backend, oracledb.thin_impl (total: 5)

On 4.0.2 the trace is the same, at connection.py, line 197, in call_timeout.

It is deterministic: 13 of 13 runs crashed for each case, on both versions. That holds whether the session is killed while idle or during a call (begin dbms_session.sleep(10); end; with call_timeout = 30000), and for setter values 0 and 5000.

These do not crash:

  • the setter on a live connection;
  • the setter on a session killed on the server whose loss the driver has not yet seen (is_healthy() still True), where the next execute raises DPY-4011 normally;
  • on the dropped connection: reading call_timeout, is_healthy(), cursor().close() and close(). ping() and rollback() raise DPY-1001: not connected to database.

Expected: an exception such as DPY-1001: not connected to database, as ping() and rollback() raise, or a no-op. Not a segfault.

4. Does your application call init_oracle_client()?

No. Thin mode.

5. Include a runnable Python script that shows the problem.

You need a second connection with ALTER SYSTEM privilege to kill the first session. Run it with python -u -X faulthandler repro.py.

import os
import time

import oracledb

user = oracledb.connect(
    user=os.environ["APP_USER"], password=os.environ["APP_PASSWORD"], dsn=os.environ["DSN"]
)
admin = oracledb.connect(
    user=os.environ["ADMIN_USER"], password=os.environ["ADMIN_PASSWORD"], dsn=os.environ["DSN"]
)

(sid,) = user.cursor().execute("select sys_context('userenv', 'sid') from dual").fetchone()
(serial,) = admin.cursor().execute(
    "select serial# from v$session where sid = :1", [int(sid)]
).fetchone()
admin.cursor().execute(f"alter system kill session '{sid},{serial}' immediate")
time.sleep(0.5)

try:
    user.cursor().execute("select 1 from dual")
except oracledb.Error as e:
    print("execute:", e)  # DPY-4011: the database or network closed the connection

print("is_healthy:", user.is_healthy())  # False
print("call_timeout:", user.call_timeout)  # reading is fine
user.call_timeout = 5000  # Segmentation fault
print("not reached")

Workaround: check is_healthy() before assigning call_timeout. It turns False at the same DPY-4011 that makes the setter fatal.

Lingua principale
Python
Stelle
455
Fork
119
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di oracle/python-oracledb

Tutte le issue di oracle/python-oracledb

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.