When I enter play mode in the Unity editor, Unity launches two instances of adb.exe (part of the Android sdk). It then closes one instance, but the other remains open. This is noticeable by having task manager open while pressing the play button in the editor.
This rogue instance of adb is never closed by Unity, and causes issues such as denying access to the editor log file, and sometimes not allowing Unity to close.
Although I have the Android SDK installed and own an Android Unity license, this issue occurs when working on a Windows project.
This has been happening since at least the first 3.5 release, as is still happening in the latest (3.5.5f3).
I have been experiencing the exact same problem, for months my Unity Editor wouldn’t close down properly, it wasn’t untill a few days ago I found out it was related to/affected by the adb.exe process. I was working with NoesisGUI addon and Unity would actually freeze up when I stopped the scene playing. Manually ending the adb.exe process would return Unity to normal and allow me to continue work. It also seems that once I had manually ended that process I didn’t have to do it again.
Hope this gets solved as it’s not very obvious whats going on and it can be quite frustrating, specially in the latter case where it would freeze up when stopping a scene playing.
I agree. It only affects me for switching between projects / shutting down so it’s not a show-stopper but I’d still like to see the back of it.
Please.
worst part is its creates thousands new connections per second, in a hour your start get connection problems in other apps if you dont terminate adb. I been using unity for many years and all the time been blaming my router for bad internet
