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: Multiple goroutines reading and writing the shared variable total without synchronization triggers a data race and undefined memory behavior under Go's race detector.
The fix: Use sync/atomic functions (atomic.AddInt64 and atomic.LoadInt64) or a sync.Mutex to synchronize access.
Remember: Plain variable arithmetic in Go is not atomic. Always use sync/atomic or mutexes for concurrent state mutation.
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/72f3ce0b-aa60-4e93-aabd-aac171783c4a" title="Debugging challenge: Unsafe atomic addition on raw float64 value" 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/72f3ce0b-aa60-4e93-aabd-aac171783c4a">TryBugHunt</a></p>