meteor 0.9 cause out of memory

[stefanocudini]

os: debian node: v0.10.28

after upgrade from 0.8.3 to 0.9 or 0.9.0.1

after run... cpu 100% for few minutes and finish every in this way:

=> Started proxy.
FATAL ERROR: JS Allocation failed - process out of memory

/opt/node-v0.10.28-linux-x64/lib/node_modules/meteorite/lib/command.js:41
            throw "Command exited with " + code + "/" + signal;
                                                      ^
Command exited with null/SIGABRT

[stefanocudini]

which version of nodejs is recommended for the 0.9.x release?

[Tarang]

Do you have 512mb ram? For the update consider using a swap file. I've seen this happen on the small digitalocean instances.

[rfox90]

Confirmed that the $5 droplet will run out of memory.

In my case the meteor app would just quit out with "Killed". Was confusing until I ran top along with it.

[stefanocudini]

@Tarang I Have 4GB of ram

[grigio]

I think I've a similar problem with cpu/ram but a different error

=> Started proxy.
=> Starting MongoDB... -
/home/user/.meteor/packages/meteor-tool/.1.0.26.1owm6lu++os.linux.x86_64+web.browser+web.cordova/meteor-tool-os.linux.x86_64/dev_bundle/lib/node_modules/fibers/future.js:173
                        throw(ex);
                              ^
Error: spawn ENOMEM
    at errnoException (child_process.js:1000:11)
    at ChildProcess.spawn (child_process.js:947:11)
    at exports.spawn (child_process.js:735:9)
    at Object.exports.execFile (child_process.js:617:15)
    at Object.exports.exec (child_process.js:588:18)
    at findMongoPids (/home/user/.meteor/packages/meteor-tool/.1.0.26.1owm6lu++os.linux.x86_64+web.browser+web.cordova/meteor-tool-os.linux.x86_64/tools/run-mongo.js:49:17)
    at findMongoAndKillItDead (/home/user/.meteor/packages/meteor-tool/.1.0.26.1owm6lu++os.linux.x86_64+web.browser+web.cordova/meteor-tool-os.linux.x86_64/tools/run-mongo.js:117:14)
    at launchOneMongoAndWaitForReadyForInitiate (/home/user/.meteor/packages/meteor-tool/.1.0.26.1owm6lu++os.linux.x86_64+web.browser+web.cordova/meteor-tool-os.linux.x86_64/tools/run-mongo.js:232:5)
    at launchMongo (/home/user/.meteor/packages/meteor-tool/.1.0.26.1owm6lu++os.linux.x86_64+web.browser+web.cordova/meteor-tool-os.linux.x86_64/tools/run-mongo.js:492:7)
    at _.extend._startOrRestart (/home/user/.meteor/packages/meteor-tool/.1.0.26.1owm6lu++os.linux.x86_64+web.browser+web.cordova/meteor-tool-os.linux.x86_64/tools/run-mongo.js:581:19)
    at _.extend.start (/home/user/.meteor/packages/meteor-tool/.1.0.26.1owm6lu++os.linux.x86_64+web.browser+web.cordova/meteor-tool-os.linux.x86_64/tools/run-mongo.js:547:10)
    at _.extend.start (/home/user/.meteor/packages/meteor-tool/.1.0.26.1owm6lu++os.linux.x86_64+web.browser+web.cordova/meteor-tool-os.linux.x86_64/tools/run-all.js:130:24)
    at Object.exports.run (/home/user/.meteor/packages/meteor-tool/.1.0.26.1owm6lu++os.linux.x86_64+web.browser+web.cordova/meteor-tool-os.linux.x86_64/tools/run-all.js:275:10)
    at main.registerCommand.name [as func] (/home/user/.meteor/packages/meteor-tool/.1.0.26.1owm6lu++os.linux.x86_64+web.browser+web.cordova/meteor-tool-os.linux.x86_64/tools/commands.js:203:17)
    at /home/user/.meteor/packages/meteor-tool/.1.0.26.1owm6lu++os.linux.x86_64+web.browser+web.cordova/meteor-tool-os.linux.x86_64/tools/main.js:1212:23

[stefanocudini]

@grigio which nodejs version are you using? and fibers version 1.0.1 or 1.0.2?

[grigio]

I'm using the versions bundled with the current

curl https://install.meteor.com/ | sh

I've 2gb ram and I've added a small /swapfile and now it seems it doesn't happen anymore.
However I use Meteor without Meterite

[grigio]

@stefanocudini have you tried to update your node version to the current supported one 0.10.29 ?
https://github.com/meteor/meteor/blob/devel/scripts/generate-dev-bundle.sh#L105

[stefanocudini]

yes! from 0.10.28 to 0.10.31 same problem :(

[grigio]

can you also test:

• a dummy app without Meteorite
• adding a swapfile https://www.digitalocean.com/community/tutorials/how-to-add-swap-on-ubuntu-12-04 ?

[stefanocudini]

maybe my issue is related to Meteor-Community-Packages/ground-db#41
solved after removing grounddb

[raix]

@stefanocudini looking into it - I'm using it production, got a deadline next week so it will be fixed - but its 0.8.3 local packages

[raix]

@stefanocudini I'm just wondering, this is a server-side issue right? it pretty limited what the grounddb does on the server-side. https://github.com/GroundMeteor/Meteor-GroundDB/blob/master/groundDB.server.js

[stefanocudini]

tnk! @raix yes I think that on server side.. maybe few regexpr that uglify-js don't recognize because some exceptions appear there.

[raix]

@stefanocudini uglyfy but your having problems on the server - is it only in production? (dont think uglify is used in dev mode) I think its an odd issue - I'm using grounddb in production, just ironing out stuff and creating better automated tests at the moment. Not sure if this issue should be closed rather mark it +0.9.0

[eahefnawy]

yeah I confirm the issue with digital ocean $5 droplet. creating a swap file worked for me, but still, memory usage is at 97% and swap usage is 80%. The droplet is only used for one meteor app.

Is that some kinda bug or what?

[ghost]

I addressed this issue by implementing the swap file as well. Using $5 Droplet and followed instructions at http://stackoverflow.com/questions/26216127/memory-issue-with-meteor-up-mup-on-digital-ocean