René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Regression bug: AbortSignal.any() causing memory leak on long lived parent signal","articleBody":"### Version\n\nv24.13.1, v25.8.1\n\n### Platform\n\n```text\nLinux KContainer 5.10.0-12-amd64 #1 SMP Debian 5.10.103-1 (2022-03-07) x86_64 x86_64 x86_64 GNU/Linux\n```\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\n\nHi,\n\nI would like to report a potential regression bug in Node. It can be reproduced by running the following snippet:\n```javascript\nconst ac = new AbortController();\n\nlet i = 0;\nfunction run() {\n  // This is the operation that causes the leak: repeatedly creating\n  // a combined signal from the same long-lived parent signal.\n  AbortSignal.any([ac.signal]);\n\n  if (++i % 100_000 === 0) {\n    const mem = process.memoryUsage().rss / 1024 / 1024;\n    const kDependantSignals = Object.getOwnPropertySymbols(ac.signal).filter(\n      (s) =\u003e s.toString() === 'Symbol(kDependantSignals)'\n    )[0];\n    const signals = ac.signal[kDependantSignals];\n    console.log(`${i} - ${mem.toFixed(2)} MiB - ${signals?.size} signals`);\n  }\n\n  setImmediate(run);\n}\n\nrun();\n```\n\n### How often does it reproduce? Is there a required condition?\n\nNo specific condition\n\n### What is the expected behavior? Why is that the expected behavior?\n\nThis issue was previously reported in #55351 and fixed in v22.12.0 'Jod' (https://github.com/nodejs/node/pull/55354)\n\n```\nroot@KContainer:~/temp/55351# node -v\nv22.12.0\nroot@KContainer:~/temp/55351# node test-any-leak.cjs\n100000 - 84.80 MiB - 19191 signals\n200000 - 95.71 MiB - 32634 signals\n300000 - 98.24 MiB - 41438 signals\n400000 - 95.88 MiB - 4510 signals\n500000 - 96.83 MiB - 13195 signals\n600000 - 97.34 MiB - 21910 signals\n700000 - 97.34 MiB - 30580 signals\n800000 - 98.64 MiB - 39250 signals\n900000 - 96.63 MiB - 2309 signals\n1000000 - 96.99 MiB - 11092 signals\n1100000 - 97.77 MiB - 19777 signals\n1200000 - 97.59 MiB - 28490 signals\n1300000 - 99.08 MiB - 37238 signals\n1400000 - 96.63 MiB - 329 signals\n1500000 - 97.71 MiB - 9057 signals\n1600000 - 98.16 MiB - 17778 signals\n1700000 - 98.16 MiB - 26520 signals\n1800000 - 99.60 MiB - 35267 signals\n1900000 - 99.43 MiB - 43989 signals\n2000000 - 97.36 MiB - 7071 signals\n2100000 - 98.04 MiB - 15770 signals\n2200000 - 97.96 MiB - 24486 signals\n2300000 - 99.22 MiB - 33191 signals\n```\n\nIt is evident from the output that memory remains constant without increasing linearly\n\n### What do you see instead?\n\nIn node v24.13.1 and v25.8.1 - Memory usage increases quickly linearly\n\n```\nroot@KContainer:~/temp/55351# node test-any-leak.cjs\n100000 - 161.09 MiB - 30167 signals\n200000 - 219.59 MiB - 43146 signals\n300000 - 295.21 MiB - 2056 signals\n400000 - 300.71 MiB - 102056 signals\n500000 - 379.02 MiB - 202056 signals\n600000 - 415.10 MiB - 56920 signals\n700000 - 423.03 MiB - 156920 signals\n800000 - 474.64 MiB - 256920 signals\n900000 - 570.81 MiB - 356920 signals\n1000000 - 621.09 MiB - 39647 signals\n1100000 - 629.51 MiB - 139647 signals\n1200000 - 630.28 MiB - 239647 signals\n1300000 - 654.92 MiB - 339647 signals\n1400000 - 740.88 MiB - 439647 signals\n1500000 - 847.48 MiB - 539647 signals\n1600000 - 922.58 MiB - 639647 signals\n1700000 - 974.05 MiB - 46721 signals\n1800000 - 981.79 MiB - 146721 signals\n1900000 - 982.41 MiB - 246721 signals\n2000000 - 992.41 MiB - 346721 signals\n2100000 - 992.41 MiB - 446721 signals\n```\n\nEventually resulting in a FATAL error:\n\n```\n\u003c--- Last few GCs ---\u003e\n\n[13503:0x6e4b000]   203625 ms: Scavenge 3702.6 (4044.6) -\u003e 3673.9 (4056.6) MB, pooled: 0.0 MB, 14.16 / 0.00 ms (average mu = 0.237, current mu = 0.225) task;\n[13503:0x6e4b000]   209229 ms: Mark-Compact (reduce) 3673.9 (4056.6) -\u003e 3447.2 (3854.4) MB, pooled: 0.0 MB, 5592.36 / 0.00 ms (+ 1.9 ms in 2 steps since start of marking, biggest step 1.0 ms, walltime since start of marking 5603 ms) (average mu = 0.238, c\nFATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory\n----- Native stack trace -----\n\n 1: 0x906a3b node::OOMErrorHandler(char const*, v8::OOMDetails const\u0026) [node]\n 2: 0xb8c2ca  [node]\n 3: 0xde4b55  [node]\n 4: 0xde82c9  [node]\n 5: 0xdfa308  [node]\n 6: 0xdf9c4f  [node]\n 7: 0x178c297  [node]\n```\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/kevgeoleo","@type":"Person","name":"kevgeoleo"},"datePublished":"2026-03-21T13:54:48.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/62363/node/issues/62363"}