Meteor.call is asynchronous. You’d have to bindEnvironment to get it to wait. Nothing in those code snippets would worry me unduly although not sure why you are returning a null. I am guessing/hoping that it isn’t production code. Probably we need more info. I guess also that that may be difficult.
I have the same problem , even though i downgraded my node versions 4.6.1 nothing changed still cpu stuck at 100% or higher for node process. I also tried 4.4.7 nothing changed .
I used nvm . then nvm install 4.6.1 . after that i used node -v command and got 4.6.1
I am running meteor just building localy and uploading tar.gz file to server then unpacking with tar command ,
then i run sudo node main.js command .
Also i dont have any user right now . If i go to website and login , after subscriptions initialized cpu goes to 100% and stays there.
In database there are only 10 to 20 data .