You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When starting a new process, the CPU usage of the daemon (Satan.js) goes up to 100%, because of an infinite loop of fs.exists() calls.
God.finalizeProcedure() calls vision.analyze() with the full pm2's exec path and then goes down to the root path, where it should stop. The stop condition only checks for /, but on Windows the root path is <disk letter>:\ (e.g. C:\) and thus the process never stops (non-stop checks whether C:\.git, C:\.hg and C:\.svn exist). Check out this output from node-tick-processor.
Hello!
When starting a new process, the CPU usage of the daemon (Satan.js) goes up to 100%, because of an infinite loop of
fs.exists()
calls.God.finalizeProcedure()
callsvision.analyze()
with the full pm2's exec path and then goes down to the root path, where it should stop. The stop condition only checks for/
, but on Windows the root path is<disk letter>:\
(e.g.C:\
) and thus the process never stops (non-stop checks whetherC:\.git
,C:\.hg
andC:\.svn
exist). Check out this output from node-tick-processor.The God.js#L440 currently looks like this:
and should be something like:
Windows 8.1 64-bit, Node.js v0.10.35, pm2 v0.12.6
The text was updated successfully, but these errors were encountered: