⚡ Bolt: Use GCD background queue for concurrent file deletion#262
⚡ Bolt: Use GCD background queue for concurrent file deletion#262acebytes wants to merge 1 commit into
Conversation
Replaced `Task.detached` with `withCheckedThrowingContinuation` and `DispatchQueue.global(qos: .userInitiated).async` in `CacheCleaner.swift`. This prevents the exhaustion of the limited cooperative thread pool caused by running multiple concurrent, synchronous blocking I/O calls (`FileManager.removeItem`), thereby eliminating potential deadlocks during large cleanups. Co-authored-by: acebytes <2820910+acebytes@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
💡 What: Replaced
Task.detachedwith a checked continuation wrappingDispatchQueue.global.asyncfor file removals.🎯 Why:
Task.detachedstays on the cooperative thread pool. Using GCD explicitly offloads blocking I/O, allowing concurrent bulk file deletion without starving the cooperative executor.📊 Impact: Prevents concurrency deadlocks during large cleanups.
🔬 Measurement: Observe UI responsiveness and lack of starvation during parallel cleanups.
PR created automatically by Jules for task 3556899244841971268 started by @acebytes