Microsite pins a CPU core on creation and building, no output
See original GitHub issueHello! Saw your post in the Preact slack, decided to give this a quick test tonight.
Unfortunately I’m having a really weird issue where Microsite appears to pin one (of my 4) CPU cores at 100% when doing any operation. I let npm init microsite microsite-test
run for about 15 minutes and all I got were fans. NPX would let me know it installed 4 deps in less than a couple seconds and then I received no more output.
I then decided to skip that and clone your template manually. Same issue. The template is unedited and after running yarn/(npm run) build
I get no terminal output and more CPU core maxing out. It does seem to cycle which core gets pinned at 100%, not sure if that’s relevant information or not. Might just be Node shuffling them.
I’ll provide my system + tool specs here, certainly let me know what else I can provide.
Environment Info:
System:
OS: Linux 5.8 Manjaro Linux
CPU: (4) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Binaries:
Node: 14.15.0 - /usr/bin/node
Yarn: 1.22.10 - /usr/bin/yarn
npm: 6.14.8 - /usr/bin/npm
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (5 by maintainers)
I’ll close this now as the problems all seem to be addressed. Thanks for your quick response, I look forward to using Microsite!
I just cloned the template manually to build and that portion does seem to be working now. Output certainly seems in-line with what I’d expect.