Searched refs:busy (Results 1 – 6 of 6) sorted by relevance
229 bool busy = false; in Clear() local232 busy = !Prune(id, 1, uid); in Clear()235 if (busy) { in Clear()
282 bool busy = false; in Clear() local285 busy = !Prune(id, 1, uid); in Clear()288 if (busy) { in Clear()
16 # failures (before memory is fragmented, and cpu is busy running tons of other
156 case, the MixActivity starts a busy thread. So we don't need to use the app while profiling.
273 used to find busy threads in a process or system wide. With `--per-thread` option, stat cmd opens
192 they have busy server load, etc. There are other internal differences between