TryBugHunt
goAsync race conditionMedium

Unexpected output in concurrent range loop processing

BugFind the bug and fix the code

What it should do

Process a slice of integers concurrently and return their squares. Example: processItems([1, 2, 3]) -> [1, 4, 9]

What happens instead

The output slice contains incorrect or duplicate values.

package main

import (
	"fmt"
	"sync"
)

func processItems(items []int) []int {
	var wg sync.WaitGroup
	output := make([]int, len(items))
	for _, item := range items {
		wg.Add(1)
		go func() {
			defer wg.Done()
			output[item] = item * item
		}()
	}
	wg.Wait()
	return output
}

func main() {
	items := []int{1, 2, 3}
	fmt.Println(processItems(items))
}

Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).

⏱️0:00
Hints
🏆 0 hints = Flawless Solve
Think & Test Cooldown
2:00 remaining

Take a moment to read the bug symptom and trace the code with Run & Check before unlocking Hint 1.

Hint 2
Unlocks after Hint 1
Hint 3
Unlocks after Hint 2

This bug belongs to the async and race conditions pattern

Goroutines racing on shared data, a WaitGroup used wrong, or a channel that deadlocks.

What you'll practise

A medium Go debugging exercise about async and race conditions: goroutines racing on shared data, a WaitGroup used wrong, or a channel that deadlocks.

The checks your fix must pass

Signs of this kind of bug

Spoiler: why this bug happens(try it first; the hints get warmer one at a time)

What went wrong: The goroutine captures the loop variable item by reference, leading to a race condition where the final value of item is used for all goroutines.

The fix: Pass the loop index and value as parameters to the goroutine to ensure each goroutine operates on its own copy.

Remember: In Go, variables in a loop are shared across iterations unless explicitly captured.

The pattern behind it: async and race conditions.

More async and race conditions to practise

Related errors

Embed this challenge on your site

Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.

<iframe src="https://trybughunt.com/embed/926c819b-8fbe-4bdc-8d60-a3b530650ada" title="Debugging challenge: Unexpected output in concurrent range loop processing" 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/926c819b-8fbe-4bdc-8d60-a3b530650ada">TryBugHunt</a></p>