The whole squid process is running under valgrind now, with leaks-check=full , so I'm seeing valgrind's analysis that way. Valgrind isn't really showing anything substantial in terms of leaks- just a few KB here and there.
If the process grows to many gigabytes as it has in the past for me, yet valgrind still shows no leaks, how do we proceed then? It would seem perhaps some piece of code is letting something grow without bounds even if not, by definition, leaking it.
-Ty
Received on Thu Sep 27 2012 - 08:18:17 MDT
This archive was generated by hypermail 2.2.0 : Thu Sep 27 2012 - 12:00:13 MDT