Runaway Node process consuming CPU #1113
Labels
impact/performance
Something is slower than expected
impact/reliability
Something that feels unreliable or flaky
kind/bug
Some behavior is incorrect or out of spec
What happened?
When running example tests in this repo I noticed 3 very long-running node processes consuming CPU on my Mac machine. This seems to be Pulumi Node language hosts as far as I can tell and they're orphan processes in the sense that their process group has terminated. I think something must be wrong with self-destruct/heartbeat machinery. Not filing it to pulumi/pulumi yet as this provider is special as the provider itself is written in Node and possibly is the culprit here.
Example
N/A
Output of
pulumi about
v3.86.0.
Additional context
N/A
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: