[2016-05-27 01:06:37-ddmlib] The software in your console aborted an established connection.
Java.io.IOException: The software in your console aborted an established connection.
At Sun.nio.ch.SocketDispatcher.write0 (Native Method)
At Sun.nio.ch.SocketDispatcher.write (Unknown Source)
At Sun.nio.ch.IOUtil.writeFromNativeBuffer (Unknown Source)
At Sun.nio.ch.IOUtil.write (Unknown Source)
At Sun.nio.ch.SocketChannelImpl.write (Unknown Source)
At Com.android.ddmlib.JdwpPacket.writeAndConsume (jdwppacket.java:213)
At Com.android.ddmlib.Client.sendAndConsume (client.java:675)
At Com.android.ddmlib.HandleHeap.sendREAQ (handleheap.java:342)
At Com.android.ddmlib.Client.requestAllocationStatus (client.java:521)
At Com.android.ddmlib.DeviceMonitor.createClient (devicemonitor.java:847)
At Com.android.ddmlib.DeviceMonitor.openClient (devicemonitor.java:815)
At Com.android.ddmlib.DeviceMonitor.processIncomingJdwpData (devicemonitor.java:775)
At Com.android.ddmlib.DeviceMonitor.deviceClientMonitorLoop (devicemonitor.java:664)
At com.android.ddmlib.devicemonitor.access$100 (devicemonitor.java:46)
At Com.android.ddmlib.devicemonitor$3.run (devicemonitor.java:592)
Cause of the problem:
This is because both Eclipse and Android Studio Two Ides are installed in the computer. The key is that when you use eclipse adb to connect to the real machine, Android Studio is also running, and the default is to connect to ADB, so the ADB is always occupied when the eclipse is connected to the real time.
Workaround:
Open the utility, Activity Monitor, locate the Android studio process, and force the shutdown.