René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`util.inspect` crashes with a getter whose `error.message` throws","articleBody":"### Version\n\nv20.19.5, v22.19.0, v24.8.0\n\n### Platform\n\n```text\nDarwin MacBook-Pro-M1.local 24.6.0 Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:29 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6000 arm64\n```\n\n### Subsystem\n\nUtil\n\n### What steps will reproduce the bug?\n\n```js\nconst error = {\n  // The error message itself is a getter that throws\n  get message() { throw new Error('Oops'); }\n};\n\nconst thrower = {\n  get foo() { throw error; }\n};\n\nutil.inspect(thrower, { getters: true });\n```\n\n### How often does it reproduce? Is there a required condition?\n\nEvery time.\n\n### What is the expected behavior? Why is that the expected behavior?\n\nSimply return the object getter as `\"\u003cInspection threw\u003e\"` without the message that threw.\n\n### What do you see instead?\n\n```console\n$ node -e 'util.inspect({get foo() { throw{ get message() { throw new Error }} }}, { getters: true })'\nnode:internal/util/inspect:1435\n    if (!isStackOverflowError(err)) throw err;\n                                    ^\n\nError\n    at get message ([eval]:1:56)\n    at formatProperty (node:internal/util/inspect:2560:51)\n    at formatRaw (node:internal/util/inspect:1428:9)\n    at formatValue (node:internal/util/inspect:1183:10)\n    at Object.inspect (node:internal/util/inspect:409:10)\n    at [eval]:1:6\n    at runScriptInThisContext (node:internal/vm:219:10)\n    at node:internal/process/execution:451:12\n    at [eval]-wrapper:6:24\n    at runScriptInContext (node:internal/process/execution:449:60)\n\nNode.js v26.0.0-pre\n```\n\n### Additional information\n\nRelated to another issue 3 weeks ago:\n- https://github.com/nodejs/node/pull/60210\n- https://github.com/nodejs/node/pull/60139\n\nThis issue also highlights robustness concerns described in [OWASP 2025 (A10 – Mishandling of Exceptional Conditions)](https://owasp.org/Top10/2025/A10_2025-Mishandling_of_Exceptional_Conditions/):\n\n\u003e Catching and handling exceptional conditions ensures that the underlying infrastructure of our programs are not left to deal with unpredictable situations.\n\nNote that I did not encounter this problem in real-world objects; I discovered it by reading the Node.js source code while investigating behavior.\n","author":{"url":"https://github.com/yvele","@type":"Person","name":"yvele"},"datePublished":"2025-11-11T19:27:40.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/60683/node/issues/60683"}