Fix daemon busy-wait loop causing 100% CPU usage#1052
Open
cetex wants to merge 1 commit intoruvnet:mainfrom
Open
Fix daemon busy-wait loop causing 100% CPU usage#1052cetex wants to merge 1 commit intoruvnet:mainfrom
cetex wants to merge 1 commit intoruvnet:mainfrom
Conversation
When a pending worker was deferred by canRunWorker() (e.g. CPU load above threshold), it was pushed back onto the pendingWorkers queue and executeWorkerWithConcurrencyControl returned null. The while loop in processPendingWorkers() immediately retried since the queue was non-empty and no workers were running, creating a tight loop that read /proc/loadavg and /proc/meminfo millions of times per second. The loop itself drove CPU to 100%, keeping load average permanently above the threshold, making it self-sustaining. Break out of the loop when a worker is deferred. The worker is already back in the queue and will be retried when the next scheduled worker completes (each worker's finally block calls processPendingWorkers). Co-Authored-By: claude-flow <ruv@ruv.net>
This was referenced Feb 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
processPendingWorkers()inworker-daemon.tsbusy-waits when a worker is deferred bycanRunWorker()(e.g. CPU load above threshold). The deferred worker gets pushed back onto the queue and thewhileloop immediately retries, creating a tight loop that reads/proc/loadavgand/proc/meminfomillions of times per second, driving CPU to 100% and making the load condition self-sustaining.breakwhenexecuteWorkerWithConcurrencyControl()returnsnull(worker deferred). The worker is already back in the queue and will be retried when the next scheduled worker completes via itsfinallyblock.Test plan
claude-flow daemon startand confirmed CPU stays low🤖 Generated with claude-flow