SystemClock.sleep() vs. Thread.sleep() while waiting for a semaphore loop

Question

In order to synchronize/queue access to a shared resource, I am about to use a Semaphore, aided by a wait loop.

In order not to run into CPU pegging, I would like t

Answer 1

The truth is:

Thread.sleep(n) could be interrupted within a call like AsyncTask by using asyncTask.cancel(true)

SystemClock.sleep(n) seems to ignore any interrupted command, thus it could be a risk of memory leak when you use it similar like here: https://github.com/square/leakcanary/blob/master/leakcanary-sample/src/main/java/com/example/leakcanary/MainActivity.java