golang-concurrency

Detect goroutine leaks and missing context cancellation by reviewing Go patches for improper channel ownership, unsafe shared state, and timer misuse. Analyze goroutine spawns and channel pipelines to identify lifecycle bugs and ensure proper context propagation.

The best way to use errgroup and singleflight involves applying correct synchronization patterns like errgroup.SetLimit for worker pools and proper singleflight implementation. Enforce channel ownership rules and context cancellation to prevent races and ensure safe shared-memory access.

Review Go channel ownership and select patterns by evaluating diffs for unsafe shared state, improper channel closure, and missing synchronization. Apply race detection techniques to channel-based pipelines and recommend appropriate mutex or atomic usage to remediate detected concurrency issues.

Use mutex or atomic primitives in Go concurrent code based on specific synchronization needs identified during code review. Recommend atomic operations for simple state protection and mutexes for complex critical sections to prevent data races and ensure safe shared-memory access.

Run parallelized audits across Go repositories to find goroutine spawns, channel ownership issues, and time.After misuse. Generate actionable remediation steps and reference-backed advice for detected concurrency bugs including leaks, races, and incorrect synchronization.