Android test apps left running on device

An investigation should be done into whether an adb shell command killed by ctest after a timeout is leaving things alive, or whether there's some DR bug leaving child processes, or what, as there are a bunch of test apps still running on my device after cron jobs and local suites over the last week:

1|shell@shamu:/data/local/tmp $ ps | grep suite                                
shell     2893  1     136908 4496   pipe_wait 4aa81288 S /data/local/tmp/build_android_dbg/suite/tests/bin/linux.signalfd
shell     15291 1     136940 4672  futex_wait b6eff530 S /data/local/tmp/build_android_dbg/suite/tests/bin/linux.threadexit2
shell     24851 1     136940 4500  futex_wait b6efe400 S /data/local/tmp/build_android_dbg/suite/tests/bin/linux.clone
shell     24882 1     136940 4504  futex_wait b6e9e400 S /data/local/tmp/build_android_dbg/suite/tests/bin/linux.threadexit2
shell     25106 1     136908 4496   pipe_wait 46e29288 S /data/local/tmp/build_android_dbg/suite/tests/bin/linux.signalfd
shell     25145 1     136940 4588     do_wait 514dd320 S /data/local/tmp/build_android_dbg/suite/tests/bin/linux.vfork
shell     25149 25145 136940 4588  futex_wait b6ee0400 S /data/local/tmp/build_android_dbg/suite/tests/bin/linux.vfork
shell     25701 1     136940 4500  futex_wait b6ea7400 S /data/local/tmp/build_android_dbg/suite/tests/bin/linux.clone