How to Resolve Go's 'All Goroutines Are Asleep' Deadlock in Goroutine Communication?

Deadlock in Go: Understanding and Resolving "All Goroutines Are Asleep"

In the provided Go code snippet, a deadlock occurs due to a misunderstanding of goroutine communication. The program aims to simulate the loading and unloading of trucks, using goroutines to handle truck unloading. However, the code fails to close the truck channel (ch) when the loading process is complete, leading to a deadlock.

To resolve this deadlock, it's crucial to close the truck channel (ch) once all the trucks have been loaded. This signals to the UnloadTrucks goroutine that no more trucks will be sent, allowing it to return.

One way to achieve this is through the use of a WaitGroup, as demonstrated in the following code:

// Define a WaitGroup to track the completion of the loading goroutines
var wg sync.WaitGroup

// Start goroutines to load trucks
go func() {
    // Load trucks and send them over the truck channel
    for t := range trucks {
        go func(tr Truck) {
            itm := Item{}
            itm.name = "Groceries"

            fmt.Printf("Loading %s\n", tr.name)
            tr.Cargo = append(tr.Cargo, itm)
            ch <- tr

            wg.Done() // Signal the WaitGroup that the loading is complete
        }(trucks[t])
    }
}()

// Use the WaitGroup to wait for all loading goroutines to complete
wg.Wait()

// Close the truck channel after all loading is finished
close(ch)

// Start the UnloadTrucks goroutine
UnloadTrucks(ch)

By closing the truck channel (ch) once all the trucks have been loaded, the UnloadTrucks goroutine is allowed to terminate, breaking the deadlock. The program will now complete successfully, unloading all the trucks as intended.

The above is the detailed content of How to Resolve Go's 'All Goroutines Are Asleep' Deadlock in Goroutine Communication?. For more information, please follow other related articles on the PHP Chinese website!