Created attachment 520108 [details] diffs for code review plus supporting information Description of problem: mod snmp under apache leaks lots of memory How reproducible: 100% Steps to Reproduce: 1. Set up apache + valgrind 2. Set up node.js + nodeload 3. Set up nodeload test script to create 10 mins / 10 million request load. 4. Run apache + valgrind 5. Run nodeload 6. Stop apache after nodeload stops 7. Analyse valgrind output Actual results: 65 MiB leak over 10 mins; 850k requests, approx 850k leaked blocks Expected results: No leaked blocks per request. Additional info: See attached for leak reports, diffs, test scripts, etc.
Created attachment 520109 [details] valgrind log showing top leaks last (look for 65 MiB leak, 852k leaked blocks)
Created attachment 520110 [details] nodeload test script used to reproduce
The final results using the patched libraries show no leaks after 10M requests: ==31157== LEAK SUMMARY: ==31157== definitely lost: 226 bytes in 4 blocks ==31157== indirectly lost: 0 bytes in 0 blocks ==31157== possibly lost: 0 bytes in 0 blocks ==31157== still reachable: 216 bytes in 2 blocks ==31157== suppressed: 0 bytes in 0 blocks
This has been fixed already; unsure why it's still open. The patch has been applied to SVN.
Looks like the fix was committed to trunk as rev 11204
verified 10/3/2011 daily build. functional test.
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE
marking VERIFIED BZs to CLOSED/CURRENTRELEASE