On 3/10/2015 1:47 a.m., Александр Демченко wrote: > Hello! > It's looks like I have memory leak on squid with peek and splice https > traffic. > I use squid 3.5.9 (try 3.5.8 and 3.5.7 also). Openssl and libresll both > tried. > CentOs 7. Traffic redirecting transparently by wccp. > Server: 8 cores, 64GB RAM. Approx 600 clients with 150 requests per second. > > Squid consume RAM without limits. Around 10MB in a second. (Screenshot from > zabbix: http://snag.gy/HQmJI.jpg) We have had a few reports of beaviour similar to this with SSL-Bump. Those turned out to be the fact that SSL contexts and sessions have a huge amount of memory state associated with them that does not get released for the lifetime of the connection. Also contexts are not shared between workers, so in your config there will be 6x the memory use for contexts. Please check if the memory goes down when all connections to the proxy are closed. Or if there is some (possibly many GB) amount where it levels off. If you still think its a leak after checking that, please try to locate a build with valgrind support. The bugzilla report will need the output from a run with valgrind. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
