Re: [squid-users] Valgrind results on 3.2.1

I just ran mgr:mem on another server that's been up for a while and does heavy traffic.

Its table of allocations accounts for about 550 MB total (which seems about like what the server should reasonably be using given my config). But my squid process on that server has, after a few days, grown to:
VIRT: 4.5g
RES: 4.5g

It is already causing swapping and needs to be restarted.

So mgr:mem seems to show that squid's memory management knows nothing about where that extra 4g of allocations comes from.

How to debug something like this? Valgrind seems not to classify these allocations as leaks, but they are there.

-Ty
Received on Thu Sep 27 2012 - 09:05:58 MDT