Time: 0:00
Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).
This bug belongs to the async and race conditions pattern
A missing await, unbuffered channel deadlocks, ConcurrentModificationException, and data races under load.
What went wrong: Thread pools created by Executors use non-daemon threads by default. If executor.shutdown() is never called, the worker threads stay alive indefinitely, preventing the JVM from terminating.
The fix: Always shut down the executor in a finally block: executor.shutdown().
Remember: Every ExecutorService must be shut down when no longer needed to allow worker threads to exit.
The pattern behind it: async and race conditions.
Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.
<iframe src="https://trybughunt.com/embed/b0c08bcb-43e8-4b81-a6fe-9e9030e2c134" title="Debugging challenge: ExecutorService thread pool prevents JVM shutdown" width="100%" height="580" loading="lazy" style="border:1px solid #d4d4d8;border-radius:12px;max-width:760px"></iframe>
<p style="font-size:14px">Debugging challenge from <a href="https://trybughunt.com/challenges/b0c08bcb-43e8-4b81-a6fe-9e9030e2c134">TryBugHunt</a></p>