Skip to main content

Demo 55

File upload backpressure bug

Ignoring stream backpressure lets upload buffers grow faster than the destination can write.

fully simulatedcurated scenariodoes not execute real code
Short answer

The readable side keeps pushing while the writable side is already behind.

Real-world bug this helps solve

A production symptom appears first: flaky tests, stale state, slow UI, late cleanup, or growing memory. This causes upload memory spikes, slow proxies, stalled file imports, and high RSS in Node services.

Common wrong assumption

Ignoring the false return value from writable.write or avoiding pipeline.

Fix direction

Fix the root scheduling, cleanup, or concurrency pattern instead of adding arbitrary waits.

Fixed code pattern
try {
  await operation();
} finally {
  cleanup();
}
Visual proof

The visual proof is the active runtime event: watch what is retained, blocked, queued, or released at each step.

How to verify in a real app

Reproduce the symptom with a small test, apply the safer pattern, then verify the flaky, slow, or leaking behavior disappears.

Share
Loading visual timeline...

Related cases

Continue with nearby confusion while the mental model is fresh.

Recommended next

Was this clear?

This stays local for now. It helps you track where the product still needs sharper cases.

Send detail