René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"ffi: toArrayBuffer() aborts on allocation failure instead of throwing","articleBody":"### Version\n\nmain\n\n### Platform\n\n```text\nmacOS 26.7.0\n```\n\n### Subsystem\n\nffi\n\n### What steps will reproduce the bug?\n\n```js\nimport { toBuffer, toArrayBuffer } from 'node:ffi';\n\ntry { toBuffer(1n, 2 ** 50); } catch (e) { console.log(e.code); }\ntry { toArrayBuffer(1n, 2 ** 50); } catch (e) { console.log(e.code); }\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\nBoth calls throw a catchable `ERR_MEMORY_ALLOCATION_FAILED`, as `ffi.toBuffer()` already does:\n\n```text\nERR_MEMORY_ALLOCATION_FAILED\nERR_MEMORY_ALLOCATION_FAILED\n```\n\n\n### What do you see instead?\n\n`ffi.toBuffer()` throws, but `ffi.toArrayBuffer()` aborts the process (exit code 134):\n\n```text\nERR_MEMORY_ALLOCATION_FAILED\nFATAL ERROR: v8::ArrayBuffer::NewBackingStore Allocation failed - process out of memory\n```\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/trivikr","@type":"Person","name":"trivikr"},"datePublished":"2026-09-30T06:32:03Z","url":"https://github.com/nodejs/node/issues/66405"}