A feature that was introduced with Unity 4.3: Hanging upon exit. Well, 4.3.1 still has that feature :s
Only thing I found out so far (also while using 4.3) is that the editor hangs itself up on exit when you have ran the game a couple of times in the editor.
…as with the 4.3 version, killing ADB.EXE from the taskmanager still allows Unity to close normally…
Happens here, too.
I hope it gets fixed in the next update…
I think it got marked as fixed after 4.3.1 released so it’s upcoming. (only took about two weeks to release 4.3.1)
Interesting information.
same problem here too.
+1
I have this problem too
I was having the same problem on both win7 and osx. The solution I read somewhere was to remove all files (*csproj, *unityproj, *sln) from your project root folder, but leaving the folders intact (such as Assets, Library, etc). Then also remove the folder Temp if present. Reopen the project and it should be fine.
As always, make a backup copy before doing this…
Let us know if it works
Found a crude work around 4.3. I start one project(dummy project). When I try to exit the first project Unity locks up. Then I start other projects I want to work on and they close without locking up unity. Then I stop the first project by stopping abd.exe. Very strange.
Anyone have performance and occlusion culling issues still? Performance was fixed for windows build, but webplayer is slow as hell.
v4.2 was 68 fps and v4.3.1 is 60 fps here in my project (rpg-style)…so its still a damn performance issue for me atleast.
Same issue here, and support told me 4.3.1 would fix it. Nope. Still happens. Frustrating.
same issue. 4.3.1 hangs upon exit. impossible loading time (slow)…
Happens to me, but seems to be more frequent if I have just saved the project/scene.
same for me, even when only using the editor and not actually ‘running’ the game or sim… seems random though.
You guys are doing better than me, finally bought pro and 4.3 crashes the AMD drivers and crashes Unity.
Try
j:\android-sdk-windows\platform-tools\adb.exe devices
This starts the adb.exe. Works for me.
If you debugging Unity process with Visual Studio, you can step forward just before JB ‘failed’ jump. When you reach this instruction, press right mouse button and click set next statement at address of MOV ESI,… then leave process running with F5. It’s work for me when Unity exit may be critical.
I hope help you.
I’ve found that running adb kill-server will let unity exit. I found this solution somewhere else and it seems to work for me.
I just open task manager and kill the adb process then unity quits properly. As long as you quit the adb process first unity will shut down properly.
This is STILL happening on the latest version of Unity. This is ridiculous, I shouldn’t have to be closing a program from Task Manager when I want to exit. It also frequently happens on changing project.
This still happen on latest Unity version. I only manage to close Unity with Task Manager. I’ve been using Windows 8.1 and this happens only with Unity.