# goroutine leak: N goroutines blocked in chan send (runtime.gopark)

- **ID:** `go/goroutine-leak-blocked-channel`
- **Domain:** go
- **Category:** resource_error
- **Verification:** ai_generated
- **Fix Rate:** 80%

## Root Cause

Goroutines send to an unbuffered channel whose receiver has exited or never runs, so they block forever. Memory and goroutine count grow unbounded over time.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| 1.7+ | active | — | — |

## Workarounds

1. **** (95% success)
   ```
   select {
case out <- v:
case <-ctx.Done():
    return ctx.Err()
}
   ```
2. **** (82% success)
   ```
   ch := make(chan int, len(producers))
// producers can always send without blocking
   ```

## Dead Ends

- **** — GOMAXPROCS controls scheduler parallelism, not goroutine blocking; blocked goroutines remain blocked. (95% fail)
- **** — Blocked goroutines are reachable from the scheduler and are not collected; GC cannot free them. (90% fail)