René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"sqlite: segmentation fault using `SQLTagStore` if there's no reference to the underlying database","articleBody":"### Version\n\nv24.10.0\n\n### Platform\n\n```text\nLinux localhost 6.17.4-200.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Oct 19 18:47:49 UTC 2025 x86_64 GNU/Linux\n```\n\n### Subsystem\n\nsqlite\n\n### What steps will reproduce the bug?\n\n```js\nimport { DatabaseSync } from \"node:sqlite\";\n\n// Creating a SQLTagStore without holding a reference to the DatabaseSync:\nconst sql = new DatabaseSync(\":memory:\").createTagStore();\n\n// Substituting line 3 with these two fixes the segfault:\n// const db = new DatabaseSync(\":memory:\");\n// const sql = db.createTagStore();\n\nsql.db.exec(\"CREATE TABLE TEST (DATA NUMBER)\");\n\n// Simulating meaningful work/likely triggering garbage collection...\nfor (const x of new Array(100_000).fill(0)) {\n  x + x;\n}\n\nconsole.log(\"About to run insert...\");\nsql.run`INSERT INTO TEST (DATA) VALUES (1)`;\n\n// Code will segfault and never run the following log\nconsole.log(\"didn't segfault!\");\n```\n\n### How often does it reproduce? Is there a required condition?\n\nRunning the snippet will always, unconditionally, cause a `SIGSEGV` on my machine.\n\n### What is the expected behavior? Why is that the expected behavior?\n\nIdeally, the program inserts the data and doesn't crash, outputting:\n```\nAbout to run insert...\ndidn't segfault!\n```\n\nIf the `new DatabaseSync().createTagStore()` usecase is unsupported, then I'd expect a user-friendly error letting me know that it's my responsibility to keep the `DatabaseSync` in scope, or some other way of preventing this unsupported pattern.\n\n### What do you see instead?\n\n`fish: Job 1, 'node index.js' terminated by signal SIGSEGV (Address boundary error)`\n\n### Additional information\n\nThe reason I tried keeping only a `SQLTagStore` is because the tag store [has a db field](https://nodejs.org/docs/latest-v24.x/api/sqlite.html#sqltagstoredb) - I liked the idea of only holding a tag store and using `sql.db` when needed, instead of holding both a `DatabaseSync` and a `SQLTagStore`.\n\nThank you for all your hard work!","author":{"url":"https://github.com/aidandenlinger","@type":"Person","name":"aidandenlinger"},"datePublished":"2025-10-28T00:49:31.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/60448/node/issues/60448"}