You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@trafficserver.apache.org by GitBox <gi...@apache.org> on 2022/03/09 23:41:15 UTC
[GitHub] [trafficserver] bryancall opened a new pull request #8719: Fixed memory leaks with CryptoContext
bryancall opened a new pull request #8719:
URL: https://github.com/apache/trafficserver/pull/8719
This fixes a memory leak when switching over to the evp functions in OpenSSL. I also removed support for the MMH hash for caches that are older than ATS 4.0.0, it was easier to remove the support. The evp function to require malloc() for the calls vs the old OpenSSL APIs that have been deprecated in OpenSSL 3. I think it is still possible to use the old APIs if you #define something.
Benchmarks of various hash implementations on an AMD Ryzen 9 3900X:
```
-----------------------------------------------------------------
Benchmark Time CPU Iterations
-----------------------------------------------------------------
openssl_old_api_md5 1312 ns 1310 ns 536272
openssl_evp_md5 1413 ns 1411 ns 497822
cryptopp_md5 1448 ns 1445 ns 485112
openssl_old_api_sha256 586 ns 585 ns 1184803
openssl_evp_sha256 681 ns 680 ns 1035870
cryptopp_sha256 606 ns 605 ns 1159814
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [trafficserver] bryancall merged pull request #8719: Fixed memory leaks with CryptoContext
Posted by GitBox <gi...@apache.org>.
bryancall merged pull request #8719:
URL: https://github.com/apache/trafficserver/pull/8719
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org