René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`AbortSignal.any()` can lose an abort when its source is garbage-collected","articleBody":"### Version\n\nReproduced on v24.16.0, v26.1.0, v26.3.1, and v26.8.2. The same example works correctly on v22.14.0, v22.23.2, v24.0.0, and v25.8.2.\n\n### Platform\n\n```text\nLinux 6.8.0-139-generic x86_64\n```\n\n### Subsystem\n\nlib\n\n### What steps will reproduce the bug?\n\nSave as `repro.mjs` and run `node --expose-gc repro.mjs`:\n\n```js\nimport { setImmediate } from \"node:timers/promises\";\n\nlet controller = new AbortController();\nconst signal = AbortSignal.any([controller.signal]);\n\ncontroller.abort(\"stop\");\ncontroller = null;\n\nawait setImmediate();\nglobal.gc();\n\nconsole.log({ aborted: signal.aborted, reason: signal.reason });\nsignal.throwIfAborted();\nconsole.log(\"throwIfAborted() did not throw\");\n```\n\n### How often does it reproduce? Is there a required condition?\n\nAlways (20/20 attempts on v26.8.2).\n\n### What is the expected behavior? Why is that the expected behavior?\n\nExpected: `{ aborted: true, reason: 'stop' }`, followed by `throwIfAborted()` throwing `\"stop\"`.\n\nThe [DOM abort algorithm](https://dom.spec.whatwg.org/#abortsignal-signal-abort) sets dependent signals’ abort reasons during abortion, regardless of whether they have listeners.\n\n### What do you see instead?\n\n\n```\n{ aborted: false, reason: undefined }\nthrowIfAborted() did not throw\n```\n\n### Additional information\n\nThe likely cause is the lazy propagation introduced by #62367: a subsequent state check cannot recover the abort reason once the weakly referenced source has been collected.\n\nI would appreciate a revert of that ASAP, until a proper fix can be included, as this is hurting jsdom pretty substantially.","author":{"url":"https://github.com/domenic","@type":"Person","name":"domenic"},"datePublished":"2026-09-12T05:17:04Z","url":"https://github.com/nodejs/node/issues/65995"}