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: Closing a channel that has already been closed causes an immediate fatal runtime panic: close of closed channel.
The fix: Ensure close() is executed at most once, guarding against closing an already-closed channel.
Remember: Channels in Go must be closed only once, and closing should typically be done by the sender.
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/4878fe99-bbcf-4dbf-80da-7964e3871b08" title="Debugging challenge: Panic on closing already closed Go channel" 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/4878fe99-bbcf-4dbf-80da-7964e3871b08">TryBugHunt</a></p>