Open v1d3rm3 opened 4 years ago
Add: Trying again today, after start command 'npm run scully', and wait changes in terminal, my computer start to freeze. Then, i open my Manager Tasks (on windows), and there was dozens of nodejs process, all of them are from scully command. It was consuming all memory of my PC, more less 12GB.
@viderme I have not heard about this issue before. From the description, it seems like a corrupted node execution. Does it still occur after you have restarted the computer?
I restarted the pc but the same thing happens. Is there any way to show some verbosity/log execution of the command? I tried the options in the cli, but nothing works. Below is a gif of execution and the processes consuming memory:
@jorgeucano Do you have any idea?
@viderme We have seen strange things with PowerShell before. Can you try it with command
or the wsl?
Also, can you try running npx scully
instead of npm run scully
?
I've tried with npx and with ubuntu terminal, same thing; I try to reproduce the bug, i thing it is related to the utilization o Rush with Angular/Scully. But no logs are being showing.
Repo: https://github.com/viderme/scully-test2
You'll need https://rushjs.io/ to work.
Some organization in monorepo, in combination with pnpm is causing the bug.
I created a project of Angular with Scully. First time i compiled, all things working perfect. Some days later, i tried to compile again, and nothing happens. I start the compilation
npm run scully
, but nothing happens: no errors, no messages. Anyone has light about this?