Re: is this a memory leak?

It is called from aclCheckCallback. aclCheckCallback itself is called from
aclCheck.

There is a logic here that you must pay more attantion to it. Suppose
that there is a leak here. As much as i know with every connection there
is an acl checking. So if there is a leak here for every connection
there we use our memory about 80 bytes. So if the load is 100 request
per second after a minute we use about 480000 bytes and after an hour
about 28M. That's imposible.

On Wed, 20 Dec 2000, Robert Collins wrote:

>
> ----- Original Message -----
> From: <cachemail@procache.com>
> To: "Robert Collins" <robert.collins@itdomain.com.au>
> Cc: <squid-dev@squid-cache.org>
> Sent: Wednesday, December 20, 2000 3:10 AM
> Subject: Re: is this a memory leak?
>
>
> > It saves a copy from that pointer in the aclCheck_t structure, when the
> > aclChecklistCreate is called.
> >
> > When aclChecklistFree is called that memory is freed.
>
> When is this called? every x minutes? at reconfigure?
>
> >
> > In the other word there are two copies from that pointer. It uses
> > the second one to free it.
> >
> > On Wed, 13 Dec 2000, Robert Collins wrote:
> >
>
>
Received on Wed Dec 20 2000 - 00:02:43 MST