[FIXED] Thread interrupt vs. JNI Function Call

Issue

I’m using the method from the accepted answer here to construct a gameloop thread.

Where to stop/destroy threads in Android Service class?

At the moment, my thread basically gets the time, makes a single Native Function call that updates the game logic, then sleeps by the adjusted passed time.

What I’m curious of, since I’m still not very comfortable with Threads, is how fast a Thread is killed with interrupt()? If it is in the middle of the code running in the Native Function, will it stop in the middle of it, or will it safely complete?

Thanks ahead of time,
Jeremiah

Solution

No worries, the documentation for interrupt says:

If this thread is blocked in an invocation of the wait(), wait(long), or wait(long, int) methods of the Object class, or of the join(), join(long), join(long, int), sleep(long), or sleep(long, int), methods of this class, then its interrupt status will be cleared and it will receive an InterruptedException.

So your thread will only get the InterruptedException if you’re in some type of blocking/sleeping/waiting state. If you’re running, the thread will not get the exception until it enters one of those states.

Your loop should be:

while(!Thread.currentThread().isInterrupted()) // <- something of the sort here
{
    try{
        // do work
    } catch (InterruptedException e){
        // clean up
    }
}

Update:
Additionally, the documentation states:

If none of the previous conditions hold then this thread’s interrupt status will be set.

Answered By – Kiril

Answer Checked By – Robin (Easybugfix Admin)

Leave a Reply

(*) Required, Your email will not be published