On 10/30/08 12:48 PM, Manik Taneja [EMAIL PROTECTED] wrote:
So it seems that there is a slow-leak perhaps we might be hitting the
problem that has been described in the following post.
http://www.nabble.com/apr-pools---memory-leaks-td19766166.html
FWIW, we always run with
Hello All,
After spending quite some time on apache and components ( specifically
mod_proxy_http, mod_mem_cache etc) we have noticed some memory leaks which
we are publishing with attached patch.
The leak can be observed when requests are sent on keep-alive connection
without closing the
On Wed, 22 Oct 2008 17:43:41 +0530
harish kulkarni [EMAIL PROTECTED] wrote:
Hello All,
After spending quite some time on apache and components ( specifically
mod_proxy_http, mod_mem_cache etc) we have noticed some memory leaks
which we are publishing with attached patch.
At a glance, this
On Oct 22, 2008, at 11:05 AM, Manik Taneja wrote:
With regards to the patch, it seems that the changes in event.c have
no effect. We have anyway seen the leak with both worker and event
mpm. The changes in scoreboard.c just ensure that memory pointed to
by new_sbh is not lost everytime
On 10/22/2008 05:33 PM, Jim Jagielski wrote:
On Oct 22, 2008, at 11:05 AM, Manik Taneja wrote:
With regards to the patch, it seems that the changes in event.c have
no effect. We have anyway seen the leak with both worker and event
mpm. The changes in scoreboard.c just ensure that memory
thanks Ruediger, I see that you have a caught another instance of the
leak.
i'll give your patch a run and let you know the results in a day or two.
Regards,
Manik
On 23-Oct-08, at 12:31 AM, Ruediger Pluem wrote:
On 10/22/2008 05:33 PM, Jim Jagielski wrote:
On Oct 22, 2008, at 11:05 AM,
On Oct 22, 2008, at 3:01 PM, Ruediger Pluem wrote:
Agreed that the mod_proxy_http.c patch looks reasonable at 1st
blush, but need to look into all possible interaction with the
change to a shorter-lived pool.
There is an explanation above the code why we should take connection-
pool,
but
Hello Nick,
Yes it's very much true that the memory allocation is happening per request
on scoreboard, and not per connection.
I think it should happen per connection level and not per request level. Yes
it could be true that it might effect other MPMs also and they may also be
facing this leak
Hello All,
After spending quite some time on apache and components ( specifically
mod_proxy_http, mod_mem_cache etc) we have noticed some memory leaks which
we are publishing with attached patch.
The leak can be observed when requests are sent on keep-alive connection
without closing the
