Nice! A little more information in case someone needs it:
Whenever your nodejs code tries to execute a shell command using child_process.exec(), a background Windows Console Host process is started. If the "legacy console" isn't enabled, then this process never finishes execution, gets stuck in memory, and uses up 10-15% of one of the cpu cores. At this point the user probably tries to start App Home again and again, which results more and more instances of conhost.exe running in the background. After a while this leads to the leap motion not working correctly due to the low cpu resources left available.