René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Node \u003e= 12.5 OSX memory spike","articleBody":"\u003c!--\r\nThank you for reporting a possible bug in Node.js.\r\n\r\nPlease fill in as much of the template below as you can.\r\n\r\nVersion: output of `node -v`\r\nPlatform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)\r\nSubsystem: if known, please specify the affected core module name\r\n\r\nIf possible, please provide code that demonstrates the problem, keeping it as\r\nsimple and free of external dependencies as you can.\r\n--\u003e\r\n\r\n* **12.5.0**:\r\n* **Darwin Quinns-MacBook-Pro-2.local 18.6.0 Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64 x86_64**:\r\n\r\n\u003c!-- Please provide more details below this comment. --\u003e\r\n\r\nWhen running a [after.js](https://github.com/jaredpalmer/after.js) app (React + babel + webpack) on OSX, can reproduce that switching from 12.4 to 12.5/12.6 that the node process spikes on initial startup in virtual memory and in some cases continues to rise until the process crashes.  12.4 stays consistent.\r\n\r\nIn looking at bugs + changes, Im suspecting v8 snapshot on osx, but have no way to determine (open to suggestions on debugging).\r\n\r\nIncluding an OSX sample of mem usage on the process\r\n\r\n[node-12.6-mem-bug.txt](https://github.com/nodejs/node/files/3362797/node-12.6-mem-bug.txt)\r\n\r\n","author":{"url":"https://github.com/chaffeqa","@type":"Person","name":"chaffeqa"},"datePublished":"2019-07-05T13:10:40.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/28558/node/issues/28558"}