I’m testing on localhost and the ‘node’ process memory is running extremely high (14GB), how can I go about debugging this?
I’m using angular2 with Meteor 1.4.3.1 on Mac
I’m testing on localhost and the ‘node’ process memory is running extremely high (14GB), how can I go about debugging this?
I’m using angular2 with Meteor 1.4.3.1 on Mac
If you can reliably reproduce this, the best thing to do is to create the smallest app that exhibits such a memory leak and file an issue! The most important thing is to figure out if this is a core Meteor thing or the result of some package.
Thanks for your reply. I have no idea whats causing it, or how to find that out… I guess I can just create a new app and start adding my components one by one until I get the leak…?
Im trying to use Kadira debug but its now crashing my app…:
W20170327-08:39:34.609(1)? (STDERR) /Users/michaelbattcock/.meteor/packages/meteor-tool/.1.4.3_1.10pxpug++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:280
W20170327-08:39:34.610(1)? (STDERR) throw(ex);
W20170327-08:39:34.610(1)? (STDERR) ^
W20170327-08:39:34.610(1)? (STDERR)
W20170327-08:39:34.610(1)? (STDERR) TypeError: Cannot read property 'createDataHandler' of undefined
W20170327-08:39:34.610(1)? (STDERR) at setLabels (packages/meteorhacks_kadira.js:3335:53)
W20170327-08:39:34.611(1)? (STDERR) at packages/meteorhacks_kadira.js:2872:5
W20170327-08:39:34.613(1)? (STDERR) at packages/meteorhacks_meteorx.js:190:7
W20170327-08:39:34.613(1)? (STDERR) at Array.forEach (native)
W20170327-08:39:34.614(1)? (STDERR) at packages/meteorhacks_meteorx.js:189:29