Time: 0:00
Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).
This bug belongs to the scope and closure bugs pattern
Every callback reports the last value, a counter never increments, UnboundLocalError on a variable you can see.
What went wrong: The lambda function captured the reference to the local variable 'processedData', which went out of scope when 'processData' returned, leading to undefined behavior when the lambda tried to access it.
The fix: Explicitly capture 'processedData' by reference in the lambda to ensure it remains in scope.
Remember: Always be cautious with reference captures in lambdas to avoid accessing variables that have gone out of scope.
The pattern behind it: scope and closure bugs.
Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.
<iframe src="https://trybughunt.com/embed/57d19e8a-78e8-4d75-b5c2-0d5213d29c33" title="Debugging challenge: Unexpected crash after function exit with lambda" 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/57d19e8a-78e8-4d75-b5c2-0d5213d29c33">TryBugHunt</a></p>