Meteor 1.0 use nearly 100% cpu when testing in local

[liyu1981]

Hi, I am playing with Meteor 1.0 in building something. I am quite happy with Meteor write less do more reactivity, but recently I have noticed that when I am testing on my Macbook Pro with OSX 10.10 Yosemite, one of the node process use nearly 100% of a cpu, which impact my battery heavily.

Here is the screenshot when I top all my processes

or check it here http://monosnap.com/image/8xasJwofVMW8fcwkU4FiWXbgh3ayuc

As I can see it that, one of the node process (the marked one) is using 100% of one of my core. And also there is another node process, which is normal.

Before digging further, I have checked my env as follows

Li-Yus-MBP:DynamicPoint yli$ meteor --version
Meteor 1.0

Li-Yus-MBP:DynamicPoint yli$ cat .meteor/packages 
# Meteor packages used by this project, one per line.
#
# 'meteor add' and 'meteor remove' will edit this file for you,
# but you can also edit it by hand.

meteor-platform
insecure
underscore
jquery
iron:router
mrt:external-file-loader
mrt:bootstrap-3
less
peerlibrary:async
accounts-facebook
accounts-github
service-configuration
meteorhacks:kadira
infinitedg:winston
liyu:sprintfjs
mrt:allow-env
livestamp
clode:transit
fortawesome:fontawesome
reactive-dict
reactive-var

As I am running Meteor on a Mac, I further digged the problematic node process with Brendan's FlameGraph. I captured 60 seconds of user-level stacks of problematic node process, and got following FlameGraph

the link:
https://cdn.rawgit.com/liyu1981/debug-meteor-node-problem/master/meteor-problematic-node-process.svg

As far as I can see, there seems to be something wrong in the fibers.node:trampoline part.

Any ideas ?

[glasser]

This is almost certainly #2135, which will be fixed in 1.1.

[liyu1981]

Thanks and wait for the fix in 1.1.