>Lock #1 is CRYPTO_LOCK_ERR, which I believe is used for logging errors.? It appears your application is generating a lot of errors for some reason.? Never tried it myself, but you probably can't disable this lock with multiple threads running.? You should take a look at the error log to identify the cause of the errors.? Then resolve the issue, whatever it may be.? I have a rewrite of the error-stack stuff that halves the number of locks. If you want to try it, drop me a line.
