Closed robinhouston closed 7 years ago
Profiling with the Chrome DevTools inspector (using node --inspect) shows that 100% of the time is spent in (program).
node --inspect
(program)
I think this may mean that whatever code is pegging the CPU is native code rather than JavaScript.
(The obvious suspect is the file watching, of course.)
Running npm rebuild in the SDK directory has made this problem disappear, presumably by rebuilding fsevents. Closing for now.
npm rebuild
fsevents
Profiling with the Chrome DevTools inspector (using
node --inspect
) shows that 100% of the time is spent in(program)
.I think this may mean that whatever code is pegging the CPU is native code rather than JavaScript.