On 10/02/2017 09:37 PM, Aaron Turner wrote: > So it's leaking memory and not tracking it? That combination (or, to be more precise, its implication) is possible but relatively unlikely in your specific case -- when GBs are leaked, there is usually something tracked related to those GBs. Please note that what Squid _tracks_ may not amount to GBs of RAM! For example, Squid can track a tiny object that is included in every large untracked leaked object. A frequent leak often manifests itself in mgr:mem snapshots as a nearly always increasing counter of alive associated objects. If you take one snapshot every 30 minutes or so, then you may be able to identify suspects by comparing same-object alive counters across 5-10 snapshots. Sorry, I do not have the time to do that for the snapshots you have shared (and you probably need a different collection of snapshots to make this search more productive). Alex. > On Mon, Oct 2, 2017 at 8:25 PM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: >> On 03/10/17 04:39, Aaron Turner wrote: >>> >>> Anyone see anything useful? >> >> >> The numbers in those reports all seem reasonable to me. Nothing is showing >> up with GB of RAM used. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
