René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"sqlite: segfault when a SQLTagStore query contains only a comment","articleBody":"### Version\n\nv27.0.0-pre (`main` @ e2d7b341640); reproduces on any build containing 8fc73417fbb\n\n### Platform\n\n```text\nDarwin 25.6.0 arm64\n```\n\n### Subsystem\n\nsqlite\n\n### What steps will reproduce the bug?\n\n```js\nconst { DatabaseSync } = require('node:sqlite');\nconst db = new DatabaseSync(':memory:');\nconst store = db.createTagStore();\nstore.run`-- comment`;\n```\n\n### How often does it reproduce? Is there a required condition?\n\nAlways. All four query methods crash: `run`, `get`, `all`, and `iterate`.\n\n### What is the expected behavior? Why is that the expected behavior?\n\nA thrown error, like the equivalent non-tag-store path produces:\n\n```js\ndb.prepare('-- comment').run();  // throws: statement has been finalized\n```\n\n### What do you see instead?\n\nA segfault:\n\n```\n* thread #1, stop reason = EXC_BAD_ACCESS (code=1, address=0x0)\n  frame #0: sqlite3_clear_bindings(pStmt=0x0000000000000000) at sqlite3.c:93850\n  frame #1: node::sqlite::SQLTagStore::ResetAndBindStatement(...) at node_sqlite.cc:3442\n  frame #2: node::sqlite::SQLTagStore::Run(...) at node_sqlite.cc:3477\n```\n\n### Additional information\n\nThe crash appears to have been introduced by #65041.","author":{"url":"https://github.com/TrevorBurnham","@type":"Person","name":"TrevorBurnham"},"datePublished":"2026-08-08T23:53:27Z","url":"https://github.com/nodejs/node/issues/65149"}