Skip to main content

Demo 54

Express slow route blocking

CPU-heavy work inside a request handler blocks unrelated requests on the same event loop.

fully simulatedcurated scenariodoes not execute real code
Short answer

The key output order is report sent -> health delayed. The route monopolizes the event loop until synchronous CPU work finishes.

Real-world bug this helps solve

A production symptom appears first: flaky tests, stale state, slow UI, late cleanup, or growing memory. This affects PDF generation, image transforms, CSV exports, encryption, large JSON parsing, and analytics aggregation in Express/Fastify APIs.

Common wrong assumption

Calling CPU-heavy synchronous work from latency-sensitive request handlers.

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 console lane proves the visible order: report sent -> health delayed. The active line and queues show why source order changed.

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