<html class="apple-mail-supports-explicit-dark-mode"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">That is not true. Go routines do not “clean up” when they cannot make progress due to no producers. Go leaks due to this are very common. </div><div dir="ltr"><br><blockquote type="cite">On Jan 12, 2026, at 4:05 AM, Alex Otenko <oleksandr.otenko@gmail.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="auto">I'd say it's not even clear why that'd constitute a bug. Whole systems are built on go-rourines and continuations getting GCed.<div dir="auto"><br></div><div dir="auto">I think there certainly is a clash between the need to track life cycle of something (tell threads to terminate) in a system where life cycle of things is not tracked (because GC).</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, 12 Jan 2026, 09:58 Viktor Klang, <<a href="mailto:viktor.klang@oracle.com">viktor.klang@oracle.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">How do you find the bug?<br>
<br>
On 2026-01-12 05:36, robert engels wrote:<br>
> Why not just fix your design to ensure the proper behavior?<br>
<br>
-- <br>
Cheers,<br>
√<br>
<br>
<br>
Viktor Klang<br>
Software Architect, Java Platform Group<br>
Oracle<br>
<br>
</blockquote></div>
</div></blockquote></body></html>