Blocking behavior in Go - Step-by-Step Execution

Concept Flow - Blocking behavior

Start goroutine or channel operation

↓

Check if resource/channel ready

↓

Block and wait

↓

Continue execution

This flow shows how Go waits (blocks) when a goroutine tries to read/write on a channel or waits for a resource until it becomes ready.

Execution Sample

Go

package main
import "fmt"
func main() {
  ch := make(chan int)
  ch <- 1
  fmt.Println("Sent 1")
}

This code tries to send a value on an unbuffered channel without a receiver, causing the program to block.

Execution Table

Step	Action	Channel State	Blocking?	Output
1	Create unbuffered channel ch	empty	No
2	Attempt to send 1 on ch	empty	Yes, blocks waiting for receiver
3	No receiver available, program waits	empty	Yes
4	Program stuck, no output	empty	Yes

💡 Program blocks indefinitely because no goroutine is receiving from the channel

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
ch	nil	empty channel	empty channel (blocked send)	empty channel (blocked send)

Key Moments - 2 Insights

Why does the program stop at step 2 and not print anything?

Because sending on an unbuffered channel blocks until another goroutine receives from it, and here no receiver exists, so the program waits forever (see execution_table step 2 and 3).

What does 'blocking' mean in this context?

It means the program pauses at that line, waiting for a condition (like a receiver on the channel) before continuing, as shown in the execution_table where the send operation waits.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the program start blocking?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Check the 'Blocking?' column in execution_table for when blocking first occurs.

According to variable_tracker, what is the state of channel 'ch' after step 2?

A nil

B closed channel

C empty channel (blocked send)

D buffered channel with 1 item

💡 Hint

Look at the 'After Step 2' column for variable 'ch' in variable_tracker.

If a receiver goroutine was added before sending, how would the execution_table change?

A No blocking; send and receive happen immediately

B Program would crash

C Blocking would still occur at step 2

D Channel would close automatically

💡 Hint

Think about how unbuffered channels synchronize send and receive without blocking if both exist.

Concept Snapshot

Blocking behavior in Go:
- Sending or receiving on unbuffered channels blocks until the other side is ready.
- Blocking pauses the goroutine at that line.
- Without a receiver, sending blocks forever.
- Adding a receiver allows send to proceed immediately.
- Blocking ensures synchronization between goroutines.

Full Transcript

This example shows blocking behavior in Go when sending on an unbuffered channel without a receiver. The program creates a channel, then tries to send a value. Because no goroutine receives from the channel, the send operation blocks and the program waits indefinitely. Variables track the channel state as empty but blocked. Blocking means the program pauses until the condition to continue is met. Adding a receiver would prevent blocking by allowing the send to complete immediately.

Practice

1. What does blocking mean in Go programming?

easy

A. Running multiple tasks at the same time

B. Waiting for an operation to finish before moving on

C. Ignoring errors in the program

D. Skipping a function call

Solution

1. Step 1: Understand the meaning of blocking

   Blocking means the program waits for something to finish before continuing.

2. Step 2: Match the definition to options

   Waiting for an operation to finish before moving on correctly describes waiting for an operation to finish before moving on.

3. Final Answer:

   Waiting for an operation to finish before moving on -> Option B

4. Quick Check:

   Blocking = Waiting [OK]

Hint: Blocking means waiting, not running or skipping [OK]

Common Mistakes:

• Confusing blocking with concurrency
• Thinking blocking means ignoring errors
• Assuming blocking skips code

2. Which of the following Go code snippets correctly shows a blocking receive on a channel?

easy

A. value := <-ch

B. go func() { <-ch }()

C. ch <- value

D. select { case ch <- value: }

Solution

1. Step 1: Identify blocking receive syntax

   Receiving from a channel blocks until a value is available, done by value := <-ch.

2. Step 2: Check other options

   go func() { <-ch }() launches a goroutine, so receive is not blocking main code. ch <- value sends, not receives. select { case ch <- value: } sends in select, not receive.

3. Final Answer:

   value := <-ch -> Option A

4. Quick Check:

   Blocking receive = value := <-ch [OK]

Hint: Blocking receive uses '<-ch' without goroutine [OK]

Common Mistakes:

• Confusing send and receive syntax
• Thinking goroutine makes receive blocking
• Using select for receive incorrectly

3. What will be the output of this Go program?

package main
import "fmt"
func main() {
  ch := make(chan int)
  go func() {
    ch <- 42
  }()
  fmt.Println(<-ch)
}

medium

A. 42

B. 0

C. Compilation error

D. Deadlock runtime error

Solution

1. Step 1: Analyze channel creation and goroutine

   A channel ch is created and a goroutine sends 42 into it.

2. Step 2: Understand blocking receive

   Main goroutine waits on <-ch until value 42 is sent, then prints it.

3. Final Answer:

   42 -> Option A

4. Quick Check:

   Send and receive synchronize, output = 42 [OK]

Hint: Send in goroutine, receive blocks until value arrives [OK]

Common Mistakes:

• Expecting deadlock without goroutine
• Thinking channel defaults to zero value
• Confusing send and receive order

4. Identify the problem in this Go code and fix it:

package main
func main() {
  ch := make(chan int)
  ch <- 10
  val := <-ch
  println(val)
}

medium

A. Compilation error due to missing import; fix by adding fmt package

B. Runtime panic due to nil channel; fix by initializing channel

C. No problem; code runs and prints 10

D. Deadlock because send blocks without receiver; fix by using a goroutine for send

Solution

1. Step 1: Understand channel blocking behavior

   Sending on an unbuffered channel blocks until a receiver is ready.

2. Step 2: Analyze code flow

   Send happens before receive, but no goroutine to receive yet, causing deadlock.

3. Step 3: Fix by sending in a goroutine

   Wrap send in go func() { ch <- 10 }() to allow receive to proceed.

4. Final Answer:

   Deadlock because send blocks without receiver; fix by using a goroutine for send -> Option D

5. Quick Check:

   Send blocks without receiver = deadlock [OK]

Hint: Send blocks if no receiver; use goroutine to avoid deadlock [OK]

Common Mistakes:

• Ignoring deadlock and expecting output
• Adding imports unnecessarily
• Thinking channel is nil

5. You want to receive from two channels ch1 and ch2 but only proceed when both have sent a value. Which approach correctly uses blocking behavior to achieve this?

hard

A. Use a buffered channel to store values from both channels

B. Use a select statement with both channels in one case

C. Receive from ch1 and ch2 sequentially: val1 := <-ch1; val2 := <-ch2

D. Receive from only one channel and ignore the other

Solution

1. Step 1: Understand blocking on multiple channels

   Receiving sequentially from both channels blocks until each sends a value.

2. Step 2: Evaluate options

   Select cannot wait for both simultaneously in one case. Ignoring one channel misses data. Buffered channel does not guarantee both received.

3. Final Answer:

   Receive from ch1 and ch2 sequentially: val1 := <-ch1; val2 := <-ch2 -> Option C

4. Quick Check:

   Sequential receive blocks until both values arrive [OK]

Hint: Receive from each channel one by one to wait for both [OK]

Common Mistakes:

• Using select to wait for both at once
• Ignoring one channel's value
• Assuming buffered channel solves blocking