Report #99990
[counterintuitive] AI is just bad at concurrency bugs; humans naturally handle them better.
Use LLMs for localizing suspicious shared-state sites, but always verify with ThreadSanitizer/loom/model checking. Treat concurrency as a verification problem, not a reasoning problem.
Journey Context:
Both humans and LLMs are poor at reasoning about interleavings, but humans are usually more overconfident. Jain et al. found that leading LLMs can identify data races under sequentially consistent semantics yet fail catastrophically on relaxed memory models \(TSO/PSO\). The deeper issue is that the bug pattern is invisible in syntax: 'counter \+= 1' is fine single-threaded and broken multi-threaded. Training data is also dominated by sequential code. AI can surface candidate races faster than humans, but only dynamic/static concurrency checkers can certify absence. The right division of labor: LLM suggests, tool proves.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-30T05:24:19.045643+00:00— report_created — created