android 中,关于线程安全退出的问题(from stack overflow)
来源:互联网 发布:网络电视盒子 编辑:程序博客网 时间:2024/05/01 19:03
原贴地址:http://stackoverflow.com/questions/680180/where-to-stop-destroy-threads-in-android-service-class
62down vote
There are several problems in the code sample you posted I will address in order:
1) Thread.stop() has been deprecated for quite some time now, as it can leave dependent variables in inconsistent states in some circumstances. See this Sun answer page for more details. A preferred method of stopping and starting a thread is as follows:
private volatile Thread runner;public synchronized void startThread(){ if(runner == null){ runner = new Thread(this); runner.start(); }}public synchronized void stopThread(){ if(runner != null){ Thread moribund = runner; runner = null; moribund.interrupt(); }}public void run(){ while(Thread.currentThread() == runner){ //do stuff which can be interrupted if necessary }}
2) Your measurements list is accessed by multiple threads (the event thread and your user thread) at the same time without any synchronization. It looks like you don't have to roll your own synchronization, you can use a BlockingQueue.
3) You are creating a new Socket every iteration of your sending Thread. This is a rather heavyweight operation, and only really make sense if you expect measurements to be extremely infrequent (say one an hour or less). Either you want a persistent socket that is not recreated every loop of the thread, or you want a one shot runnable you can 'fire and forget' which creates a socket, sends all relevant data, and finishes. (A quick note about using a persistent Socket, socket methods which block, such as reading, cannot be interrupted by Thread.interrupt(), and so when you want to stop the thread, you must close the socket as well as calling interrupt)
4) There is little point in throwing your own exceptions from within a Thread unless you expect to catch it somewhere else. A better solution is to log the error and if it is irrecoverable, stop the thread. A thread can stop itself with code like (in the same context as above):
public void run(){ while(Thread.currentThread() == runner){ //do stuff which can be interrupted if necessary if(/*fatal error*/){ stopThread(); return; //optional in this case since the loop will exit anyways } } }
Finally, if you want to be sure a thread exits with the rest of your application, no matter what, a good technique is to call Thread.setDaemon(true) after creation and before you start the thread. This flags the thread as a daemon thread, meaning the VM will ensure that it is automatically destroyed if there are no non-daemon threads running (such as if your app quits).
Obeying best practices with regards to Threads should ensure that your app doesn't hang or slow down the phone, though they can be quite complex :)
- android 中,关于线程安全退出的问题(from stack overflow)
- VS中出现Stack overflow的问题
- stack overflow的问题
- stack overflow的 问题
- 关于线程安全退出
- 关于线程安全退出
- Visual Studio 2005中,关于堆溢出(Stack overflow)问题的解决
- 关于堆溢出(Stack overflow)问题的解决
- 关于线程退出的问题
- VS2005 stack overflow的问题
- VS2005 stack overflow的问题
- VC2008 的 stack overflow 问题
- VS2005 stack overflow的问题
- Debug Stack Overflow的问题
- FreeLibraryAndExitThread DLL中线程的安全退出
- FreeLibraryAndExitThread DLL中线程的安全退出
- FreeLibraryAndExitThread DLL中线程的安全退出
- 线程的安全退出
- Unity3d在Android上发布
- ORACLE安装测试
- JQuery Autocomplete使用Ajax例子
- ASP.NET MVC中使用jQuery时的浏览器缓存问题
- 第一个DOS中断处理程序(中断号为0)
- android 中,关于线程安全退出的问题(from stack overflow)
- 控件变量和程序成员变量是如何交换数据的?
- 关于捉虫大赛的蛋疼想法
- Qt下学习OpenGL之OBJ模型
- C#简单读写文件
- 夢追い人作者诸葛兵心
- 罗杰斯言(转)
- Qt下OpenGL贴图问题
- Android 存储文件数据与读出文件数据