"Status: N/A" over and over and over...

Mac OS 10.9.1, Galaxy Nexus, Android 4.2.2, ADP 0.3.1 and 0.3.2

What steps will reproduce the problem?
Disconnecting and reconnecting the phone will eventually get it in to a state 
where ADP.app just says "Status: N/A", even on a fresh launch, and does not 
change regardless of actions taken.  Eventually, ADP.app will respond to clicks 
but cannot be quit without a force quit.

What is the expected output? What do you see instead?
In the past I've been able to disconnect and reconnect the phone a few times, 
and if it ever got in to an odd state I'd just relaunch ADP on the phone and 
Mac and they'd be fine.  It may be less reliable under OS 10.9, but I'm not 
quite sure what changed.

Please provide any additional information below.
It is fairly common to have 6-10 adb processes running after several attempts 
to relaunch ADP and get it working again.  It did once return to a functional 
state after I upgraded from 0.3.1 to 0.3.2 but died again after a few 
reconnects.

I get this in the console when force-quitting ADP.app:
1/15/14 1:18:55.232 PM com.apple.launchd.peruser.503[178]: 
(com.google.android.desktop.proofer.34528[14902]) Exited with code: 143

Original issue reported on code.google.com by emi...@neurostyle.net on 15 Jan 2014 at 9:19

Akash049 / android-ui-utils

"Status: N/A" over and over and over... #209