search

duckdb / duckdb-node

MIT License
34 stars 22 forks source link

Closing a connection fails #52

Open dusadrian opened 4 months ago

dusadrian commented 4 months ago

Hi all,

This is an issue following this DuckDB discussion, and it might also be related to Issue: https://github.com/duckdb/duckdb-node/issues/39

What happens is, after successfully closing a connection the first time, any subsequent connection cannot be closed anymore. To reproduce, please clone this quick repo.

After the usual npm install to get all necessary node packages, use npm start to start the application and push the button. After no longer than 30 seconds, the database lock is released and I can connect using either CLI from the Terminal, or from another API such as the duckdb package in R.

However, after the first lock being released, for any subsequent button push (therefore any subsequent database connection), the lock is not released anymore no matter how much time one waits.

This was tested on MacOS on both Intel and ARM computers, using Sonoma. The DuckDB version is the latest, 0.10.0 (as per the package.json file in the above repo.

In hoping this can be reproduced, Adrian

jeffreytkj commented 4 months ago

I am having the exactly issue with v0.8.1 & the latest versions. I was tested on MacOS also.

t-samuelg commented 3 months ago

any updates? I'm facing the same problem. I try to create a database on the fly and then export the whole database file.

hilkeheremans commented 1 week ago

Confirm, can reproduce on macOS and inside docker containers of all sorts