[gnutls-devel] GnuTLS | Thread local storages not free'd until application exits (#824)

Development of GNU's TLS library gnutls-devel at lists.gnutls.org
Fri Aug 30 16:14:19 CEST 2019

Dave Craig created an issue:

  When random.c moved to using thread local storage it started allocating storage whenever gnutls_rnd was called on a new thread. It keeps track of these allocations in a list so that when the application exits it can free them all up. Hopwever, if an application calls gnutls_rnd on a different thread each time (e.g. HLS over HTTPS with GStreamer) then memory is eaten up at a few hundred bytes per call, and is only recovered when the application ends.
I've reverted random.c for now, as my posix_ TLS based patch was too ugly. Using the tss_xxx functions for those with C11 should resolve this in a straightfoward way.

Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/issues/824
You're receiving this email because of your account on gitlab.com.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20190830/8efffc69/attachment.html>

More information about the Gnutls-devel mailing list