Repository navigation
Node >= 12.5 OSX memory spike #28558
Description
Activity
@nodejs/platform-macos @joyeecheung
Can you capture a core dump and use https://github.com/nodejs/llnode/ to try listing all types of objects with
v8 findjsobjects? If the instance becomes too big usingulimit -vto limit the virtual memory allowed should be helpful.Alternatively, you can try building Node.js with
--without-node-snapshotin theconfigureoption, and use that to see if the issue reproduces with a no-snapshot build. The guide on building Node.js is https://github.com/nodejs/node/blob/master/BUILDING.md#building-nodejs-on-supported-platforms(which reminds me it should be possible to make this a run-time option)
- added a commit that references this issue
on Jul 9, 2019 - added a commit that references this issue
on Jul 20, 2019 - Reacted by Quinn Chaffee
When running a 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.
In looking at bugs + changes, Im suspecting v8 snapshot on osx, but have no way to determine (open to suggestions on debugging).
Including an OSX sample of mem usage on the process
node-12.6-mem-bug.txt