I did a little more debugging into this one and it seems that for every HTTP POST request that gets reverse proxied, we lose a mem block from the bucket allocator list which eventually causes the apr_bucket_alloc() code to invoke malloc(). This leak only happens if there is data in the request body that gets POST'ed. Eg. UserName=user1
I've opened up a bugzilla bug report, #24991. Any insights or clues to help track this down would be very much appreciated.
From: Larry Toppi [mailto:email@example.com]
Subject: Mem Leak when reverse proxying HTTP post requests
I'm running the JMeter stress test tool to create HTTP POST requests through Apache (v.2.0.48) on the Windows 2000 platform. The request posts a small amount of data to a web page. Apache is configured to reverse proxy (ProxyPass) the request to the backend web server. In doing so, it seems that Apache leaks memory. Has anyone seen this or knows why this is happening? This memory leak does not happen when reverse proxying HTTP GET requests.