Time: 0:00
Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).
This bug belongs to the async and race conditions pattern
A missing await, unbuffered channel deadlocks, ConcurrentModificationException, and data races under load.
What went wrong: Calling wg.Add(1) inside the launched goroutine creates a race condition with wg.Wait(). If wg.Wait() executes before the goroutines execute wg.Add(1), it sees a counter of 0 and returns immediately.
The fix: Call wg.Add(1) synchronously in the parent goroutine before spawning the worker goroutine, and protect completed with a mutex.
Remember: Always call sync.WaitGroup.Add() before starting the goroutine whose completion it will await.
The pattern behind it: async and race conditions.
Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.
<iframe src="https://trybughunt.com/embed/4b7e3039-3fbd-4ab7-8ea0-97c5d57f8737" title="Debugging challenge: WaitGroup Add inside goroutine creates race condition" width="100%" height="580" loading="lazy" style="border:1px solid #d4d4d8;border-radius:12px;max-width:760px"></iframe>
<p style="font-size:14px">Debugging challenge from <a href="https://trybughunt.com/challenges/4b7e3039-3fbd-4ab7-8ea0-97c5d57f8737">TryBugHunt</a></p>