Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deadlock when opening a 2nd connection with an unclosed statement from previous connection #101

Open
juja0 opened this issue Oct 22, 2024 · 0 comments

Comments

@juja0
Copy link

juja0 commented Oct 22, 2024

Not sure if this is expected behaviour but if a new connection is opened when a prior (closed) connection has an unclosed statement, the request hangs.

Properly closing all statements before closing connections seems to fix the deadlock.

Could potentially be related to the busy-wait added in this PR.

Wanted to check if it would be better to have a configurable timeout for the busy wait since the cause of deadlock may be hard to pin down when it hangs.

Sample repro: https://github.com/juja0/duckdb_deadlock

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant