Performance testing of check-in and check-out show that mod-patron-blocks creates and holds on to HTTP Clients. Attached is a heap-dump memory-leak-suspect report mod-patron-blocks_Leak_Leak_Suspects.zip generated by the Eclipse heap dump tool showing HttpClientImpl and ConnectionMananager objects being held in memory. This problem was found in the Goldenrod release.
steps to reproduce
Run the check-in-check-out performance test for over an hour. This test calls the following API which incurs the memory leaks: /automated-patron-blocks/
. So, technically, calling this API over and over again in an hour would generate the leaks.
No memory leaks over time