[External] : Re: Virtual thread memory leak because TrackingRootContainer keeps threads

[robert engels]

Btw - this thread sounds like you’re annoyed. That was not my intent. I’m sorry if I annoyed you. I hope you had a wonderful 4th. 

> On Jul 4, 2024, at 4:43 PM, robert engels <robaho at icloud.com> wrote:
> 
> I’m sorry I don’t follow. I thought I explained  benefit of observabiluty with regards to lifecycle but I guess I didn’t. I don’t think that comment was helpful -  maybe it’s just me.
> 
>> On Jul 4, 2024, at 1:44 PM, Ron Pressler <ron.pressler at oracle.com> wrote:
>> 
>> 
>> 
>>>> On 3 Jul 2024, at 18:27, robert engels <rengels at ix.netcom.com> wrote:
>>> 
>>> I agree 100% - I am fighting that the auto-closing of the queues, clean-up, etc is “unneeded magic”
>> 
>> There is no auto-closing, no cleanup, and no magic. If a thread gets stuck in a state where it can never be observed or continued — so if it is NOT waiting on a queue to which something could be enqueued because in that case the thread COULD possibly continue — then whether that thread consumes some inaccessible bytes in memory or not is the same as far as functionality is concerned.
>> 
>> To compare it to a magic trick, this is about as magical as me asking you to pick a card from a deck without looking at it and then torching both your card and the deck and telling you that I know your card had some suit and either a face or a number.
>> 
>> — Ron
>>