httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From (Rodent of Unusual Size)
Subject Re: [PATCH] plug for mod_example memory leak
Date Fri, 18 Apr 1997 18:55:24 GMT
>From the fingers of "Roy T. Fielding" flowed the following:
>Well, it improves it -- now it only grows 1.5MB per child and then
>stays near constant.

    Although far from ideal, and not as good as I'd expected, at least
    the leak seems to be plugged.  I'd guess that it's as big as that
    because malloc()'s pre-grabbing a big chunk to parcel out in
    subsequent requests.  But that's just a guess.

>                      Note that this is on requests that are not
>within the
>   <Location /example-info>
>   SetHandler example-handler
>   </Location>
>Is there any way to prevent it from building a trace when the request
>is not under that location?

    At the moment, I don't see how without peering into other phases.
    Doing the above also wouldn't address cases of "AddHandler .example"

>                             If not, then I'd suggest just removing
>the trace parts that occur before the request pool is allocated.

    Then you lose a lot of the information it's trying to demonstrate.
    Unless I can figure out a way to do the first thing you suggested,
    my take at this point would be to say that, "mod_example is merely
    for illustration purposes, and the 1.5MB hit per child is the cost
    of using it.  Once you have an handle on the process and have
    achieved Understanding of Digital Watches, take mod_example out of
    your configuration."

    #ken    :-/}

View raw message