I have been working on this problem a couple months now and could really use some advice.

 

The problem basically manifests when you turn OpenSSL caching on and the leak is very substantial – multiples of 8k, megabytes per day.

 

I realize this could be mod_ssl misbehaving.

 

Does anyone know if mod_ssl should be setting up the following callbacks in the threaded model?

 

  1. CRYPTO_set_dynlock_create_callback
  2. CRYPTO_set_dynlock_lock_callback
  3. CRYPTO_set_dynlock_destroy_callback

 

Mod_ssl does call CRYPTO_set_locking_callback, is this sufficient?

 

Any help is appreciated.

 

BTW – I have not been able to prove it conclusively; though, it looks like the un-freed memory is being allocated by CRYPTO_malloc. I am not sure if this means mod_ssl is doing or not doing something it should?

 

-ken

Reply via email to