WiiLi.org

[Kintar]

Hey, Cha0s. If you've got time, one thing that would be really cool in the next version of WiiRemoteJ would be something that lets the WiiRemote's worker threads shut down when the remote disconnects. One of the project I'm fiddling with will require that the remote be an optional device, even being disconnected in the middle of a run, only to be reconnected later. I've noticed that there's something hanging on out there when the remote is disconnected, both through the WiiRemote.disconnect() call, and if the remote is powered down via its power button, leaving the possibility of a bunch of threads dangling out on the edges of nowhere until a System.exit() is called.

Oh, and if I'll certainly admit to the possibility of missing something in the documentation and causing this issue on my own, so let me know if that's the case.

-- Kintar

[Cha0s]

I'm pretty sure that all the threads kill themselves. The main listener thread has special instructions on how to kill itself gracefully. Any other active threads will probably throw exceptions when the remote is disconnected and die peacefully after that. There are only two threads that loop, one being the listener and one being the readSoundData thread. However, the latter thread would also throw an exception if the remote disconnected mid-sound-playing. AND, it also has as one of the conditions of the loop, "connected," so it should definitely go away. I don't think there should be anything left after a disconnect. I could be missing a thread somewhere, but I'm pretty sure that's all of them. It may be that they just haven't been cleaned up by garbage collection. Try calling Runtime.getRuntime().gc() and see if they go away then.
_________________
Cha0s