René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"process.constrainedMemory() should map UINT64_MAX to 0, per node documentation","articleBody":"### Version\n\nv22.17.1\n\n### Platform\n\n```text\nLinux#32-Ubuntu SMP Wed May 28 19:48:56 UTC 2025 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\nExecute process.contrainedMemory() on any linux machine without any defined constraints.\n\n### How often does it reproduce? Is there a required condition?\n\nWhen there is a constraining mechanism, but there is no constraint set\n\n### What is the expected behavior? Why is that the expected behavior?\n\nAccording to node documentation, If there is a constraining mechanism, but there is no constraint set, 0 should be returned\n\n### What do you see instead?\n\nnode\nWelcome to Node.js v22.17.1.\nType \".help\" for more information.\n> os.totalmem()\n2003443712\n> process.constrainedMemory()\n18446744073709552000\n>\n\n### Additional information\n\n[This](https://github.com/nodejs/node/blob/main/src/node_process_methods.cc#L244) code should be amended\n\nLibuv doc: https://docs.libuv.org/en/v1.x/misc.html#c.uv_get_constrained_memory\nNode doc: https://github.com/nodejs/node/blob/main/doc/api/process.md?plain=1#L1086","author":{"url":"https://github.com/Asaf-Federman","@type":"Person","name":"Asaf-Federman"},"datePublished":"2025-07-26T16:26:13Z","url":"https://github.com/nodejs/node/issues/59227"}