TryBugHunt
goAsync race conditionMedium

Loop variable captured by reference in goroutine

BugFind the bug and fix the code

What it should do

Spawn worker for each integer in list and return collected values. Example: spawnLoopWorkers([1, 2, 3]) -> [1, 2, 3]

What happens instead

All goroutines capture the final loop variable value 3

package main

import (
	"fmt"
	"sync"
)

func spawnLoopWorkers(nums []int) []int {
	var wg sync.WaitGroup
	var mu sync.Mutex
	results := make([]int, len(nums))
	for i, val := range nums {
		wg.Add(1)
		go func() {
			defer wg.Done()
			mu.Lock()
			results[i] = val
			mu.Unlock()
		}()
	}
	wg.Wait()
	return results
}

func main() {
	fmt.Println(spawnLoopWorkers([]int{1, 2, 3}))
}

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 closure captures i and val by reference. Because the loop continues running while goroutines are scheduled, all goroutines observe the final iteration's values.

The fix: Pass i and val as explicit arguments into the anonymous goroutine function.

Remember: Always pass loop variables as arguments to goroutines to bind their value per iteration.

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/4ca2e150-cb68-4035-a3fe-6fff84b4acaf" title="Debugging challenge: Loop variable captured by reference in goroutine" 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/4ca2e150-cb68-4035-a3fe-6fff84b4acaf">TryBugHunt</a></p>