The reported crash (for v14.9.9) does not happen in EVP_cleanup(),
even though the instrumented code apparantly said so, but the
actual cause was a memory access on an already freed pointer that
sneaked into the release (which has not seen thorough testing,
also apparantly).