Meteor crash
My Meteor app crashes with the following error:
Unexpected mongo exit code null. Restarting.
=> Exited from signal: SIGKILL
/home/ron/.meteor/packages/meteor-tool/.1.1.3.4sddkj++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/fibers/future.js:245
throw(ex);
^
Error: Unable to allocate ArrayBuffer.
This is followed by a call stack trace.
What is causing this?
Thank!
source to share
This error is likely caused by your operating environment. If ArrayBuffer fails to allocate it, it may be that you have insufficient RAM or some other service is blocking Meteor memory allocation.
This error can occur on the smallest DigitalOcean blob if that's what you are using.
It is generally recommended that you have 1GB of free bar for Meteor to work properly in development mode.
Something you can use is a swap file to make your ram grow.
source to share
Real RAM can be swapped out for virtual memory but won't be as fast memory ... on linux this SO feature is achieved using a swap partition. Windows uses a paging file. From above, you can emulate this feature in the Linux world using swapspace (or create a traditional swap partition )
sudo apt-get install swapspace
Whichever option you choose will create a swap for you and this will help you get your meteor application running.
Just keep in mind that this will be a slower experience than real RAM, but will definitely work
source to share