On 12/21/21 7:48 PM, Praveen Ponakanti wrote: > We are running the squid proxy for servicing outbound HTTP quests from > our network and have observed a significant memory leak with 5.x > versions. While there are several discussions about memory leaks with > recent versions, just wanted to list out what we have observed in case > this is an unknown leak. I recommend sharing a log with 48+ hourly mgr:mem snapshots. These snapshots help compare your leak with others we know about and may help isolate some of the memory leaks: https://bugs.squid-cache.org/show_bug.cgi?id=5132#c8 > I have attempted to build squid with -with-valgrind-debug, and run it in > a test env. However valgrind appears to collect some data from the parse > config functions and then the squid proxy restarts. FWIW, valgrind works as expected in my environment. If your Squid proxy is killed by an assertion or crashes, even in a test environment, please consider reporting that bug (after checking that it has not been reported already, of course). If your test proxy is misconfigured, then please fix the configuration before proceeding with tests. Thank you, Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
