Re: memory leak associated w/running any ecap adapter

> Do you get the same kind of "possibly lost" valgrind record when running
> the same test with eCAP disabled? If not, do you at least get the smake
> kind of memory growth?

No, I do not get the same growth or possibly lost. Below is the valgrind
summary by simply setting "ecap_enable off" and commenting out the
"loadable_modules /path/to/ecap_adapter_passthru.so".

==10646== LEAK SUMMARY:
==10646== definitely lost: 108 bytes in 4 blocks
==10646== indirectly lost: 276 bytes in 21 blocks
==10646== possibly lost: 6,232 bytes in 84 blocks
==10646== still reachable: 1,034,445 bytes in 7,652 blocks
==10646== suppressed: 0 bytes in 0 blocks

I'll re-run all these with the valgrind --num-callers 50 option as you
suggest.

--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/memory-leak-associated-w-running-any-ecap-adapter-tp4657812p4657842.html
Sent from the Squid - Development mailing list archive at Nabble.com.