-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CPU 100% while application is running idle #8244
Comments
Okay, I partially found the cause. I have a dependency tree somewhat like:
Package i.e. this configuration resolves the high CPU usage.
However, this should in theory give me the exact same result as the original configuration. So this is either a bug in I'll see if I can make a reproduction |
I had the same issue and it turned out to be Node version (I saw you on the forum commenting as well). Once we went back to v4.6.2 all worked. Also, Kadira output didn't make sense too. |
Can we close? Thanks |
Since it sounds like a solution/workaround has been found for the original issue, I'll close this off. If you're able to put together a repro showing this issue further, we can definitely re-open if needed. Thanks for posting this originally (and thanks again for the follow up @ramezrafla!). |
I have a similar problem since a long time for now. I think since version 1.3 or so. I'm not sure when it's started exactly. I've already tried to find the root of the problem, but without any luck. $ sudo errinfo -c -p 75338
Tracing... Hit Ctrl-C to end.
^C
EXEC SYSCALL ERR COUNT DESC
node stat64 2 253949 No such file or directory I've went a little deeper and ran
It seems, that the build tool is scanning every directory of my app (maybe just only the Edit: I'm using Meteor 1.6.1 on OSX |
Some people have reported 100% CPU usage in a meteor app, without the app actually having to do any work.
I ported my app from Meteor 1.2 to Meteor 1.4.2.3, and I'm now also experiencing this problem.
I have it both in development mode and in a production build (so just running the node bundle inside a docker container).
I've been able to take a CPU profile that I can share via kadira, I hope this can help to trace the problem:
https://ui.kadira.io/cpf/5rcLdo3apwSTJHn9s?metric=costlyFunction
This is from a production build, where the app is basically doing nothing (no clients connected)
Meteor version: 1.4.2.3
Node version: 4.6.1
Additionally, I see that in the production it's at 100% right from the start.
In development mode, it's at around 30% on my i7 machine, as soon as I load the app on 1 client it goes to 100% and stays there, even if I close the page.
The text was updated successfully, but these errors were encountered: