How to Prevent Deadlock in Golang When Using Goroutines and Channels?

Solving Goroutines Deadlock

When working with concurrent Golang programs, you may encounter a deadlock error: "fatal error: all goroutines are asleep - deadlock!". This error occurs when multiple goroutines are waiting on each other to perform a task, creating a deadlock situation.

Consider the following code:

<code class="go">func producer(ch chan int, d time.Duration, num int) {
    for i := 0; i <p>This code creates two producer goroutines that send values to the same channel. The main goroutine continuously receives values from the channel in an endless loop.</p>
<p>The problem arises because the producers are "short-lived" and stop sending values after a finite amount of time, but the main goroutine continues receiving values endlessly. This creates a deadlock since the channel is never closed to signal that no more values will be sent.</p>
<p>To solve this deadlock, we must ensure that the channel is closed when all producers have completed their tasks. The efficient way to achieve this is to use a synchronization primitive like a sync.WaitGroup.</p>
<p>Here's a modified version of the code:</p>
<pre class="brush:php;toolbar:false"><code class="go">func producer(ch chan int, d time.Duration, num int, wg *sync.WaitGroup) {
    defer wg.Done()

    for i := 0; i <p>In this code, we pass a sync.WaitGroup to each producer goroutine. Each producer increments the waitgroup before starting and decrements it when it finishes. The main goroutine waits for the completion of all producers using wg.Wait(). Once all producers have finished, the main goroutine closes the channel.</p>
<p>This solution ensures that the channel is only closed after all producers have completed their work, preventing a deadlock situation.</p></code>

The above is the detailed content of How to Prevent Deadlock in Golang When Using Goroutines and Channels?. For more information, please follow other related articles on the PHP Chinese website!