[squid-users] leaking memory in squid 3.4.8 and 3.4.7.
Amos Jeffries
squid3 at treenet.co.nz
Wed Oct 1 12:54:58 UTC 2014
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2/10/2014 1:19 a.m., Michele Bergonzoni wrote:
>> I have an external ACL defined as: external_acl_type preauth
>> cache=0 children-max=1 concurrency=100 ttl=0 negative_ttl=0 %SRC
>> %>{User-Agent} %URI %METHOD /usr/sbin/squid-preauth
>
> It is well known that external ACLs with ttl=0 and cache=0 leak
> RAM: I had this problem and discovered the reason only recently,
> but Amos knows it since 2011:
>
> https://www.mail-archive.com/squid-dev@squid-cache.org/msg14809.html
>
>
If you read the next post in that thread you will see the referenced
patch was dropped. IIRC it always produced a non-match result in some
configs.
An updated variant is present in 3.4 which still produces a useful
result in all cases. The leak is probably from that.
> I recently opened a bug about this, that I will update now:
>
> http://bugs.squid-cache.org/show_bug.cgi?id=4088
>
> A workaround that we use and may be applicable in your case is to
> use ttl=1 cache=1.
>
Thank you for the reminder. I will start work on this next.
Amos
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUK/miAAoJELJo5wb/XPRjTeMH/jxUyS/7Bn14nYC3zkR6O4Oi
LPjCSKVxsOpjyr0577bmvYwmCEC6KEOO5cwoPUXNPys4OuZ8w4nQjo98Jsh1yF4n
/atpPWS+qOFXwHgvgU1SPlxbl3hB44jQCuOQPqgtX7ZQff4c4z7EbH03Ieq2Y9pq
6S8jo+jtAN4p9kRgnhgLy1uMM4mP3uM4mFKimkY3f5seQynL02+xzFamqEpxzoUU
87cieyHRy4okicC2VvAg33/ErpXJLAfYswF+pbZcOqxnerbI08mXK9HeCkXuATUB
v1z4HEJKlZijJFUr9DfZ4d9ara/abQUiVs8gr+kDBRDF51i3F235VxWDdGSHjxU=
=DPXu
-----END PGP SIGNATURE-----
More information about the squid-users
mailing list