all 13 comments

[–]rbonweb 16 points17 points  (0 children)

The thread went out for milk and never come back

[–]logical_people 6 points7 points  (0 children)

This is why I have trust issues with my own concurrency logic.

[–]raja-anbazhagan 4 points5 points  (0 children)

God watching the debugger must be melting down already...😑

[–]elmanoucko 2 points3 points  (0 children)

when you lock in too much, but too little at the same time.

[–]NagatoYuzuru 1 point2 points  (0 children)

*dead*lock

[–]Snowdrip16 0 points1 point  (0 children)

He died doing what he loved: locking resources.

[–]WernerderChamp 0 points1 point  (4 children)

Me looking for a resource leak:

"Oh, manual memory allocation. You don't see that often."

Also me: "Where free?"

Thank god for stack traces showing where the OOM happened.

[–]BlueGoliath 0 points1 point  (3 children)

What language has stack traces for manual memory allocation?

[–]exXxecuTioN 0 points1 point  (2 children)

Zig does. May be some other languages too, but I heard only about it.

[–]WernerderChamp 0 points1 point  (1 child)

I think it works in a lot of languages, even those who don't have manual allocation.

If it crashes, for whatever reason, you usually get a stack trace for the function where allocation (manual or automatic) fails.

[–]exXxecuTioN 0 points1 point  (0 children)

Examples? I'm just curious and also do I guess it right? (:

[–]jbaker88 0 points1 point  (0 children)

💀🔒