How to Avoid Deadlock in Go Goroutines When Producers Are Short-Lived?

Resolving Deadlock in Go Goroutines

In concurrent programming, deadlock occurs when multiple goroutines wait indefinitely for each other to complete operations, effectively halting the program. This article addresses a specific deadlock encountered in Go concurrency, as described in the original question:

<code class="go">package main

import (
    "fmt"
    "time"
)

func producer(ch chan int, d time.Duration, num int) {
    for i := 0; i <p>This code triggers a deadlock error due to the following factors:</p>
<ul>
<li>The producers, which send values to the channel, are short-lived and eventually stop producing data.</li>
<li>The endless for loop in the main function continuously receives values from the channel without a termination condition.</li>
<li>The channel is closed after the endless loop, resulting in no further values being available for receiving.</li>
</ul>
<p><strong>Solution: Coordinated Termination</strong></p>
<p>To avoid deadlock, the producers must be coordinated to signal completion, and the channel must be closed by the last producer. Here's an efficient solution using a sync.WaitGroup for coordination:</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 solution:</p>
<ul>
<li>We increment the WaitGroup for each producer.</li>
<li>Each producer decrements the WaitGroup upon completion through a defer statement.</li>
<li>A goroutine waits for the WaitGroup to reach zero (meaning all producers are done) and closes the channel.</li>
<li>The main loop uses a for range construct to iterate over the values sent on the channel before it is closed.</li>
</ul></code>

The above is the detailed content of How to Avoid Deadlock in Go Goroutines When Producers Are Short-Lived?. For more information, please follow other related articles on the PHP Chinese website!