On 10/8/21 4:56 AM, Steve Hill wrote: > > I'm seeing high memory usage on Squid 5.1. Caching is disabled, so I'd > expect memory usage to be fairly low (and it was under Squid 3.5), but > some workers are growing pretty large. I'm using ICAP and SSL bump. As Ralf Hildebrandt mentioned, this is a known problem that we are tracking as Bug 5132: https://bugs.squid-cache.org/show_bug.cgi?id=5132 We have fixed a few related bugs and will submit polished fixes for the official inclusion soon, but those fixes do not seem to solve the primary problem. We do not know what causes the primary leak, but still have some suspects to go through, and continue to work on this issue. > I've got a worker using 5 GB which I've collected memory stats from - > the things which stand out are: > - Long Strings: 220 MB > - Short Strings: 2.1 GB > - Comm::Connection: 217 MB > - HttpHeaderEntry: 777 MB > - MemBlob: 773 MB > - Entry: 226 MB > What's the best way of debugging this? I cannot recommend anything specific at sysadmin level right now because the tricks I knew about (that would often work at that level) did not help in this particular use case. > It there a way to list all of the Comm::Connection objects? The exact answer is "no", but you can use mgr:filedescriptors as an approximation. Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
