You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this issue is to track the growth in memory usage when running npm test, which has lead to increasing the node memory as a stop gap
i was able to make some progress isolating the gc memory issue- maybe we make a separate issue to track it
by executing nyc mocha with the --node-command inspect to enable debugging i was able to connect a memory profiler and get a GC snapshot and allocation timeline
the majority of the growing heap usage seems to be coming from SourceMapConsumer in node_modules/source-map/lib/source-map-consumer.js at the bottom of a pretty long call stack that includes @ babel/core
i found meteor/meteor#9568 potentially relevant link that has encouraging similarities.
by changing nyc.instrument=false in package.json on line 51, the memory never exceeded 600MB, while re-enabling that line eventually balloons up to 12GB which was the most i was willing to test.
i will continue investigating upgrading our source-map indirect dependency so we can hopefully get this resolved
The text was updated successfully, but these errors were encountered:
this issue is to track the growth in memory usage when running
npm test
, which has lead to increasing the node memory as a stop gapThe text was updated successfully, but these errors were encountered: