# goroutine leak: goroutine blocked on channel send

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

## Root Cause

A goroutine sends to a channel that no one receives, often because the receiver exited early or the channel is unbuffered and no reader is active.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| 1.18 | active | — | — |
| 1.21 | active | — | — |

## Workarounds

1. **** (92% success)
   ```
   Use select with context cancellation:
select {
case ch <- val:
case <-ctx.Done():
    return
}
   ```
2. **** (88% success)
   ```
   Ensure the receiver always drains the channel or closes it to unblock senders. Use a done channel to signal shutdown.
   ```

## Dead Ends

- **** — Only delays the leak; if buffer fills, goroutine still blocks. (70% fail)
- **** — Leaks accumulate over time, causing memory growth and eventual OOM. (90% fail)