On 28.09.14 08:34, Eliezer Croitoru wrote:
Also to minimize the leak source try to share more information about your usage. Are you using SMP workers or not? What is the mem and info options in the cache manager page data? Did you tried "cache deny all" acl to minimize the source of the leak?
For what its worth, I'm also seeing a big memory leak on multiple servers under Squid 3.4.6:
I have two basic Squid configurations - one of them is a plain caching proxy and is _not_ leaking. The other does no caching, but is doing ICAP, external ACLs, SSL bumping and TPROXY and leaks like a sieve (several gigabytes a day).
I _think_ I have narrowed it down to something ICAP related and I'm currently valgrinding. Unfortunately I can't seem to get the valgrind instrumentation to work so I'm having to do without (I compile --with-valgrind-debug but "squidclient mgr:mem" doesn't produce a valgrind report). I have noticed that there are a _lot_ of memory errors reported by valgrind though (uninitialised memory).
Pretty much all of the leaky memory is showing up as unaccounted: Memory accounted for: Total accounted: 84306 KB 3% memPool accounted: 84306 KB 3% memPool unaccounted: 2917158 KB 97% I am using SMP workers, but turning that off doesn't fix the issue. -- - Steve Hill Technical Director Opendium Limited http://www.opendium.com Direct contacts: Instant messager: xmpp:steve@xxxxxxxxxxxx Email: steve@xxxxxxxxxxxx Phone: sip:steve@xxxxxxxxxxxx Sales / enquiries contacts: Email: sales@xxxxxxxxxxxx Phone: +44-844-9791439 / sip:sales@xxxxxxxxxxxx Support contacts: Email: support@xxxxxxxxxxxx Phone: +44-844-4844916 / sip:support@xxxxxxxxxxxx _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
