René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"sqlite: prevent reentrant statement finalization from callbacks","articleBody":"### Version\n\nmain\n\n### Platform\n\n```text\nmacOS 26.5.2\n```\n\n### Subsystem\n\nsqlite\n\n### What steps will reproduce the bug?\n\n```js\nimport { DatabaseSync } from 'node:sqlite';\n\nconst db = new DatabaseSync(':memory:');\n\ndb.function('close_database', () => {\n  console.log('callback: closing database');\n  db.close();\n  console.log('callback: database closed');\n});\n\nconsole.log('before query');\ndb.prepare('SELECT close_database()').get();\nconsole.log('after query');\n```\n\n### How often does it reproduce? Is there a required condition?\n\nAlways\n\n### What is the expected behavior? Why is that the expected behavior?\n\n`close()` should reject or defer finalization while statement execution depth is non-zero; `db.deserialize()` should apply the same protection.\n\n### What do you see instead?\n\n```console\nbefore query\ncallback: closing database\ncallback: database closed\nSegmentation fault\n```\n\n`db.close()` finalizes the prepared statement while that same statement is executing inside `sqlite3_step()`, and the process subsequently crashes.\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/trivikr","@type":"Person","name":"trivikr"},"datePublished":"2026-07-28T02:46:28Z","url":"https://github.com/nodejs/node/issues/64795"}