I’m using the UE4 at Windows PC 8.1 x64. I noticed that when I use the program, the system has adb.exe (android debugging) and the UE4.exe working in system.
But when I close the program, the adb.exe and UE4.exe files not automatically close and continue to work in system background. I need close it manually.
Hey Hermes_Hum,
Thank you for reporting this issue. Just need to ask you a couple of questions so we can further investigate. What version of UE4 are you currently using? Could you also included your DXdiag? Do you have a step by step way of reproducing this issue? Any additional information would be greatly appreciated.
Thanks and have a great day!
Ty for the reply Sean.
UE 4.4.0
I start launcher UE4, okay no problem, then choose a project, the engine works well.
The problem is when I shut the engine, right top I choose Close.
I go check the Task Manager the adb.exe and Unreal Engine still working, they don’t close properly.
If I start the engine again, adb.exe and Unreal Engine duplicate at Task Manager.
When I close the 2th Unreal Engine, it disapear at Task Manager, but the adb.exe don’t close, so I will have alote adb.exe working at background and always 1 Unreal Engine.
Maybe I’m being methodical, but I think this is not normal. When I close the program it should close all tasks because it’s no longer necessary, will only occupy memory if active.
link text
Hey Hermes_Zum,
I have attempted a reproduction of this issue on Windows 8.1 but have been unsuccessful with so. Would you be able to see if this occurs when you restart your system and try this on a fresh slate? Also, Have you attempted to uninstall and re-install the engine? These are just some ways to troubleshoot what you may be seeing.
Is your 4.4 build a GitHub build or no?
Thanks!
Hey Sean,
My 4.4 build isn’t GitHub.
I think I found the problem. It’s the adb.exe that don’t let Unreal Engine close. So it’s a Android SDK problem.
Because if I don’t have the Android SDK then the UE4 works fine. I’m using the Android SDK Nvidia that is in the extras folder.
Howdy again Hermes_Zum,
Thank you for reporting this issue. I have been successful when trying the new repro of this issue even on Windows 7 (this is what i am currently running off of). It does seem that adb.exe will not close once that editor has been opened and the issue is being caused by the SDK.
I have written up a bug report for the issue so that it may be fixed in a future release of UE4.
Thanks again and have a great day!
Once adb.exe starts running, it will stay running in the background in server mode. It is expected that it just stays around (google made it that way). If you go into the Task Manager and turn on the Command Line column, what does it say is the command line? I expect “adb fork-server server”.
I don’t see any way that adb would be keeping UE4 from properly closing. Why do you think adb is keeping the engine open?
I’ve been researching the problem and ask in some forums, it seems that is a common problem in some programs.
Unity3D had the same problem until they have found a solution some time ago.
Certain UE4 will find a solution soon.
If you can find any info on how others have solved the problem, let me know 
Okay, what I was trying before wasn’t working, it turns out that Visual Studio was keeping it open. Anyway, I have an idea now on how to fix this…