Well, the error message is for sharedWorkerThread and the code is sharedPrioThread and I admit I've never actually done exactly this, however I strongly suspect that this is the Android-ended-your-process issue.
When Android sees more than a certain number of processes running in background (14 on my ICS Galaxy) it starts killing them off. They are restarted in new processes as needed. The new process will need its state re-initialized. ...note, btw, that calls to quit() don't have anything to do with the value of the field (I presume) sharedPrioThread. Why are you lazily initializing the field? I have to say that, one of the best things that is coming from the Java communities' interactions with Android is that they may, finally, quite lazily initializing everything. It makes programs more complex and it is only rarely useful. if sharedPrioThread were static final initialized at creation, I don't think you'd have the problem. G. Blake Meike Marakana The second edition of Programming Android is now on-line: http://shop.oreilly.com/product/0636920023005.do -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
