-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Git call running 100% CPU #1177
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
Comments
It comes from the vizion module which grabs metadata about the repository. |
It does indeed refresh the metadata at each restart. |
Normally, these commands are really fast, they shouldn't stay on htop for long but just in case there is a timeout of 60s by default to cancel them if they did not succeed. |
The installed vizion version is |
@jshkurti we should reduce the timeout to 5-3secs instead of 60s |
Change timeout to 5 seconds instead of 60 Unitech/pm2#1177
@janders223 we will implement a |
Hi @janders223, check out the new release of PM2 https://github.com/Unitech/PM2/releases |
While I appreciate the work, this seems like a band-aid for a larger underlying problem. Have you spent any time at all to investigate the actual issue reported here? |
What happens when you |
Hmm actually vizion isn't supposed to execute multiple parallel instances but when a restart occurs we refreshed the flag value. |
That seems to have helped. |
Thanks for the feedback 👍 |
PM2: 0.12.10
IOJS: v.1.5.1
OS: Ubuntu 12.04.4 LTS
I am seeing this with a crashed process that is attempting to restart. It seems to be coming from:
https://github.com/keymetrics/vizion/blob/07638d9e90e969829fee36ad0912e5464667186b/lib/git.js#L27
I honestly don't see what the git log has to do with attempting to restart a crashed process, or why it chews up CPU.
The text was updated successfully, but these errors were encountered: