线程中断与 JNI 函数调用 [英] Thread interrupt vs. JNI Function Call

查看:148
本文介绍了线程中断与 JNI 函数调用的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

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

解决方案

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.

这篇关于线程中断与 JNI 函数调用的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆