"Not Responding" after disconnecting Wiimote

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Connect Wiimote
2.Disconnect at any time by taking battery out
3.Attempt to access the menu

What is the expected output? What do you see instead?
Output expected is to be able to access the menu. Instead, attempting to click 
gets you "Not Responding," and trying to force quit freezes the computer 
completely.

What version of the product are you using? On what operating system?
Version 0.6 on Mac OS X 10.7.5

Please provide any additional information below.
Even attempting to restart the computer leaves you hanging at the white screen 
with loading circle. Forcing a shutdown manually is the only way to turn your 
computer off once application is "not responding." Also noticed an incredible 
temperature spike, with fans spinning 3834rpm, temp shot from 28 Celcius to 55 
C. Hope that helps pinpoint the issue. 

Original issue reported on code.google.com by abrya...@gmail.com on 23 May 2013 at 2:25

[GoogleCodeExporter]

Hello!

It's occur only, if you taking battery out? Can you test it with my test.app 
(http://code.google.com/p/wjoy/downloads/detail?name=test.zip)?

Original comment by alexandr.serkov on 23 May 2013 at 6:37

[GoogleCodeExporter]

I've used the app, and followed the same steps.

-Connect
-Disconnect by taking battery out

The application immediately went to "Not Responding," but pulled out of it
before long, about 30 seconds. I did it again, and the application hung at
"Not Responding" indefinitely. I attempted to force quit, and I'm not sure
if the computer froze after that, or only input from my bluetooth keyboard
and mouse was interrupted. The clock still changed time, the temperature
was shown to be rising, and my Apple Magic mouse's green light was blinking
as if it was trying to connect to the computer.

Shutting down the computer with the physical button was the only solution.

Hope this helps,

Bryan

Original comment by abrya...@gmail.com on 23 May 2013 at 8:22

[GoogleCodeExporter]

Thanks, Bryan! I reproduced behavior like this on 10.8.3. And i will try to fix 
it :)

Original comment by alexandr.serkov on 24 May 2013 at 7:43

• Changed state: Accepted

[GoogleCodeExporter]

I did research and found out that the problem in the bluetooth stack. I'll try 
to think about this problem, and maybe i'll find workaround for this bug. Sorry 
:(

Original comment by alexandr.serkov on 26 May 2013 at 8:45

• Changed state: WontFix

[GoogleCodeExporter]

Yahoo! I did find way to fix it. In 0.7.1 i'll fix it, with bug #10.

Original comment by alexandr.serkov on 30 Jun 2013 at 7:06

• Changed state: Fixed