Search squid archive

Re: leaking memory in squid 3.4.8 and 3.4.7.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hey Steve,

Can you share the basic cache manager requests statistics and the up time for the service?
(mgr:info)

This would give us a basic idea of the load\requests needed to reproduce it.

Eliezer

On 09/29/2014 12:04 PM, Steve Hill wrote:
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.

_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users





[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux