I encountered this problem at work earlier this week. Googling brought me to a few people who thought the term “CPU leak” was appropriate. If you know of an established term please let me know 🙂
We use gulp to build our app at Koho and I usually turn it on to watch my files and forget about it, only closing it at the end of the day or if I was going to work on something else.
I also don’t restart my MacBook Pro very often. I haven’t had any performance issues from only using sleep before.
I was wondering why the fans were kicking in on my computer, even though I wasn’t doing anything out of the ordinary. My battery was also dieing very quickly.
Looking at activity monitor I noticed gulp had 120 threads and was using 75% of a CPU with the kernal_task using (persumably) the rest of that core. The numbers would vary but the two together always seemed to be close to 100% utilization. A fresh instance of gulp uses 0.1% as most of the time it is only watching for changes.
I am not sure on how to replicate the bug, but I will keep an eye on gulp CPU % to see if I notice a specific thing that causes it to go up. It seems to be a known issue at least.
I am interested in the concept of a bug that could cause a program to consume more and more CPU resources. I get the concept of a memory leak, where you allocate resources but neglect to deallocate when you are done with them.
I wonder if there can be an analogy or if the situations are too unsimilar as to make it absurd to compare them.