You are not logged in.
Pages: 1
``gulp serve`` refuses to die with ``kill -9`` or even with ``sudo systemctl reboot --force``.
This happens when ``gulp serve`` has been running for a while - it looks for file changes in a folder. By running it and then running ``touch test.md`` (it watches md files) it can easily get to 1.6 Gis of ram after which it becomes unkillable.
When shutting down, the shut down would hang with the message ``systemd-shutdown[1]: Waiting for process: 114556 (gulp serve)``. This message is repeated periodically. I need to shut it down via the power button to actually get it to shut down.
Offline
Is the process in the Uninterruptible Sleep (D) State?
Offline
Yes, it shows ``DNL`` in ps stat column.
Offline
Offline
I might be misunderstanding, but this issue seems to be related to ``npm install``, rather than running a process via ``npm start``.
It also seems to be more of a general issue from what I see posted there, where I can reproduce it almost conisistently - I just need to do additional testing to see what are the minimum things I need to do to reproduce it.
Offline
No, the issue cited can happen in *any* node process, not just 'npm install'. If you scroll down, you'll see that this issue was closed in reference to this libuv issue, which appears to be the culprit.
Offline
The uninterruptible state seems to be a (6.6) kernel bug triggered by this - are you using the LTS kernel and do you get the same behavior w/ 6.11 or in doubt 6.10?
Offline
I'm using 6.6.59-1-lts, I can test with non-lts kernel.
Offline
Is the kernel issue resolved in linux-lts 6.6.60-1 currently in core-testing?
Offline
Pages: 1