Thanks David,
#4 seems to be the simplest solution to me.
while trying #4, I get exception on windows platform. Usually the excpetion
occurs in ERR_clear_error while allocating memory.
I call ERR_remove_state() at end of library functions. With single thread it
works find. But as soon as I increas
Pankaj Aggarwal wrote:
> I am able to think about the following approaches :
> 1. Keep a record a threads which are spawned.
> 2. Expose a function from our library for cleanup when the thread exits
> Is there any other way to avoid the memory leak caused by error queues ?
There are severa
