Hi,
I've been fixing up some leaks in QA today, after being bitten by
some wierd behaviour resulting from tests not cleaning up.
Ken, I think I have a fix for the long-standing dbus-daemon leak
we were talking about awhile back (results from dbus-launch hackery
in common.qt); just testing it now. Heads up that thats pending,
it may be dbus-launch version specific, but I hope not.
Frank, test 666 is leaking pmmgr and valgrind processes ...
root 17496 1 0 Mar16 ? 00:00:00 /bin/sudo -E valgrind -q
--leak-check=full --read-var-info=yes --gen-suppressions=all
--suppressions=/var/lib/pcp/testsuite/valgrind-suppress --vgdb=no --log-fd=1
/usr/libexec/pcp/bin/pmmgr -v -v -p 5 -l /tmp/666-17457.out -c
/tmp/666-17457.dir
pcp 17501 17496 0 Mar16 ? 00:03:27 valgrind -q --leak-check=full
--read-var-info=yes --gen-suppressions=all
--suppressions=/var/lib/pcp/testsuite/valgrind-suppress --vgdb=no --log-fd=1
/usr/libexec/pcp/bin/pmmgr -v -v -p 5 -l /tmp/666-17457.out -c
/tmp/666-17457.dir
I have two of those for every test run over the last few days. It
looks like sudo's parent was killed, rather than the pmmgr child,
since its been reparented to init.
cheers.
--
Nathan
|