Apologies for the delay in responding - I have not had reliable Internet or VPN access for a few days, as well as being on holiday. I have attempted to run valgrind in a lab setting with the given parameters, but I found that it eventually it locked up the entire machine, so it is possible that I won't be able to run under valgrind. That was on a virtual machine though, so I will attempt running it on a proper hardware based machine to see if it helps at all - I will come back on Monday with more information. Thanks, Nathan. -- Nathan Hoad Software Developer www.getoffmalawn.com On Mon, Dec 23, 2013 at 4:52 PM, Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > On 12/22/2013 12:39 AM, Nathan Hoad wrote: >> On Wed, Dec 18, 2013 at 4:54 PM, Alex Rousskov wrote: >>> I recommend the following next steps: >>> 1. Set "memory_pools off". >>> 2. Disable all caching with "cache deny all". >>> >>> Do you see as similar memory growth pattern after the above two steps? > > >> I do see a similar pattern, although slowed [...] I'm >> happy to go in the other direction and raise the size of the memory >> pools, if that could be something useful. > > No, please keep memory pools off and caching disabled for as long as you > can -- it simplifies triage. > > >> I have got an ALL,9 log, but I am hesitant to unleash it on anyone as >> it is a 20gb file, from start to stop. If there is interest, I can >> still upload it - it compresses down to 1.7gb. > > I will email you upload instructions privately. > > >> Running valgrind produces repeated, spurious errors > > Could be a platform-specific issue, bit if you have not ./configured > Squid --with-valgrind-debug and --disable-optimizations, please do so > and repeat the valgrind test. If valgrind works after that configuration > change, post or upload the resulting valgrind log (keeping Squid's > debug_options at ALL,1). > > Here is a valgrind configuration that you may find useful (adjust as > needed): > >> valgrind -v >> --trace-children=yes >> --num-callers=30 >> --log-file=valgrind-%p.log >> --leak-check=full >> --show-reachable=no >> --suppressions=valgrind.supp > > The suppression file is attached (it is outdated and incomplete but > probably still helps). > > Please note that valgrind slows Squid down a lot. > > > Thank you, > > Alex. >
