Message279922
Quote from https://github.com/curl/curl/issues/964
---
I wrote to Matt Caswell from openssl.org about this memleah, and he answered:
OpenSSL maintains a separate error queue for each thread. On each queue there can be
multiple errors. ERR_get_state() does not add any errors to the queue it
merely returns the ERR_STATE (i.e. the queue) for the current thread.
If the current thread has no queue then ERR_get_state() will create one.
ERR_clear_error() removes all the errors that are on the current
thread's queue. It does not deallocate the current thread's queue.
ERR_remove_thread_state() deallocates the specified thread's queue.
The mem leaks you are seeing are almost certainly because the queues for
your app's threads have not been deallocated.
---
The memory leak only affects OpenSSL 1.0.2 and older. OpenSSL 1.1.0 takes care of threading, locking and thread local resources itself. |
|
Date |
User |
Action |
Args |
2016-11-02 12:01:30 | christian.heimes | set | recipients:
+ christian.heimes |
2016-11-02 12:01:29 | christian.heimes | set | messageid: <1478088089.97.0.896254141092.issue28588@psf.upfronthosting.co.za> |
2016-11-02 12:01:29 | christian.heimes | link | issue28588 messages |
2016-11-02 12:01:29 | christian.heimes | create | |
|