[KinoSearch] memory use
Marvin Humphrey
marvin at rectangular.com
Sun Jan 24 10:49:31 PST 2010
On Sat, Jan 23, 2010 at 07:04:02PM -0800, Marvin Humphrey wrote:
> That's why we have test_valgrind... only the suppressions file
> trunk/devel/conf/kinoperl.supp has been wrong since the switch to
> LockFreeRegistry, so test_valgrind is currently broken.
As of r5749, test_valgrind is fixed and passes. I found a few small memory
leaks here and there, but nothing that would cause a jump from 80 MB to 600
MB. Does this problem also persist after a "./Build realclean"?
Marvin Humphrey
More information about the kinosearch
mailing list