concurrency-review

To find race conditions and deadlocks before shipping, analyze concurrent code for unsynchronised shared-state access, unsafe closure capture, and incorrect lock ordering cycles. This review detects silent data corruption and resource leaks across async and threaded execution.

Reviewing async cancellation propagation requires validating correct waiting patterns, missing cancellation paths, and completion mechanisms that never resolve. The review targets language-specific signals across JS/TS, Python, Java, C#, C++, Go, and Rust.

Yes, you can check synchronization primitive errors and message-passing patterns in Go and Rust. The review validates correct use of locks, atomics, channels, queues, and messaging shutdown behavior across threaded execution and message-passing architectures.

A static analysis review for thread safety is needed when concurrent code risks silent data corruption, broken cancellation, or resource leaks. It classifies findings as Blocking, Recommendation, or Observation with actionable fixes for race conditions and lock ordering.

Detect distributed locking errors and unsafe closure capture by reviewing concurrent code for atomicity violations, incorrect waiting patterns, and synchronization primitive misuse. The analysis targets async interleavings, threaded execution, and distributed locking patterns.

Concurrency review works with both async interleavings and threaded execution models. It validates synchronization, messaging best-practices, and cancellation propagation across async, threaded, message-passing, and distributed locking patterns in multiple programming languages.