TryBugHunt
goAsync race conditionMedium

Unexpected zero value in concurrent Go program

BugFind the bug and fix the code

What it should do

Process data concurrently and collect results. Example: processConcurrentResults(data) -> []int

What happens instead

The program unexpectedly returns zero values in the result slice.

package main 

import (
	"fmt"
	"sync"
)

func processConcurrentResults(data []int) []int {
	resultChan := make(chan int)
	var wg sync.WaitGroup
	for _, d := range data {
		wg.Add(1)
		go func(d int) {
			defer wg.Done()
			resultChan <- d * 2
		}(d)
	}
	wg.Wait()
	close(resultChan)
	result := make([]int, len(data))
	for i := 0; i < len(data); i++ {
		result[i] = <-resultChan
	}
	return result
}

func main() {
	data := []int{1, 2, 3}
	result := processConcurrentResults(data)
	fmt.Println(result)
}

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 code reads from a closed channel without checking if the channel is still open, leading to unexpected zero values.

The fix: Use the two-value receive pattern to check if the channel is open before reading from it.

Remember: Always use the two-value receive pattern when reading from channels to handle the case where the channel might be closed.

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/d73c65b5-b955-4a4e-98ca-ddda33818778" title="Debugging challenge: Unexpected zero value in concurrent Go program" 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/d73c65b5-b955-4a4e-98ca-ddda33818778">TryBugHunt</a></p>