Bug: 100% CPU usage after first run following new install
(On development machine, from source directory.)
npm run install-locally
site enable test/siteor or
site global test/siteor
What should happen
Site.js should barely register on CPU usage.
What actually happens
CPU usage rapidly climbs to and stays at 100%.
The current workaround is to disable and re-enable. Whatever is causing the spike only appears to be manifesting when a new Site.js binary is installed and the enable command is used for the first time:
site disable site enable test/site
I think this might be due to how we’re handling the automatic privilege escalation which restarts the app and keep the original app in an endless while loop. The latter might be causing the CPU spike?
- Test this.