| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
This PR fixes a mutex deadlock issue in the job manager where calling job.Stop() while holding the runningJobs mutex could block all job operations if a job was stuck in runOnce().
Key Changes:
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sorry, something went wrong.
(cherry picked from commit 510f134)
| Back | FazBrowse Home | New Git URL |
The manager previously called job.Stop() while holding the runningJobs mutex.
Since Stop() is a blocking call—it waits until the job’s goroutine exits—this created a scenario where a job stuck in runOnce() could hold the mutex for an extended time.
Summary
Test Plan
Additional Information
For users: How does this change affect me?Summary by cubic
Moved job Stop() out of the runningJobs mutex to avoid blocking the manager when stopping slow or stuck jobs. This keeps other jobs responsive during stop operations.
Written for commit eaf7bd4. Summary will update automatically on new commits.