Classic298 2355b8a369 fix: requests hang or fail with 503 after pages are closed while loading (#32617) ...

Closing a page while the server was still sending it data (a file's processing status, a chat export) could interrupt a database read halfway. On SQLite the connection used for it was then never given back, and a later unrelated request could hang forever when that connection was finally cleaned up; once enough were lost, every request needing the database waited 30 seconds and failed with a 503. The connection is now kept and rolled back instead of being thrown away inside the interrupted request, and the session is closed once instead of twice, as either alone still lost connections. Closing 600 chat exports and 300 file status streams mid-load on SQLite used to lose 60 (the whole pool in that test) and 56 connections, now none; Postgres lost none before or after.

Fixes #32609

2026-10-21 03:23:05 +09:00

..

db.py

fix: requests hang or fail with 503 after pages are closed while loading (#32617)

2026-10-21 03:23:05 +09:00