Marc,

Post refcount release bug, I've been looking more closely into the implementation of tls contexts, and I have a couple of questions

1. The tls context contains internally allocated data, that is released immediately with ___release_rc_tls_context in failure paths of ___os_make_tls_context.
    However, I am not convinced it gets cleaned up when the tls context is reclaimed by the gc.

    Is there a finalizer for tls contexts or do we leak that internal memory?

2. Is there a need to make a tls context per socket or can the tls context be reused and shared among many (concurrent) sockets?

    Currently I make a new context every time I make an https request, but it would be very nice if a single context could be

    reused.

-- vyzo