While playing the game, the unity editor just stays in hung state at random times. Attaching the status of the process of Unity, the status of the process is ‘Tx’. I am not sure what is causing that to happen…
The only way to fix it is to restart the Mac to open the project. This is rather annoying.
I am using Unity 2019.2.12f1 on Mac OS X 10.15.1 ( Catalina OS X ).
Please let me know if there is any workaround to kill the process without restarting the machine.
I have tried killing the process using ‘Kill’ command in terminal… also the ‘Kill -9 ’. Nothing seems to work.
This is happening to me too on 2019.2.3f1. Unity crashes when I am editing in Animator tab, and it takes the system down hard: force-quitting it does not work (the icon disappears but the window stays on and the mac keeps spinning), terminating on terminal does not work (same result). Only thing I can do is restart the mac.
2019.2.3f1 on Mac OS 10.15.3 Catalina.
@mukultictoc did you file a bug report? So I can add onto there.
Same problem here with Unity 2018.4.17f1 under MacOS 10.15.3
I force quit Unity, the icon disappears from the Dock but Unity windows stay there and I can hear the MBP fan screaming…
If I open Activity Monitor it hangs as well (this happens only when I have this problem with Unity).
Trying to kill the process by terminal doesn’t have any effect.
Oof, this is happening to me as well, since (finally) upgrading to Catalina this weekend. I’m unable to open Activity Monitor (it hangs forever); my fans are going full speed, and ps -x | grep Unity reports a bunch of processes that cannot be killed even with kill -9 pid:
41351 ?? TXs 5:47.86 /Applications/Unity/Hub/Editor/2019.3.9f1/Unity.app/Contents/MacOS/Unity -projectpath /Users/tim/export/the_hunt/TheHuntGame -useHub -hubIPC -cloudEnvironment production -hubSessionId 63c28ea0-7f44-11ea-a4f5-535fbe72d9e5 -accessToken (redacted!)
41352 ?? R 5:40.17 /Applications/Unity/Hub/Editor/2019.3.9f1/Unity.app/Contents/Frameworks/UnityLicensingClient.app/Contents/Resources/Unity.Licensing.Client --namedPipe Unity-LicenseClient-tim
41353 ?? S 0:09.58 /Applications/Unity/Hub/Editor/2019.3.9f1/Unity.app/Contents/Resources/PackageManager/Server/UnityPackageManager -s 41351 -p 50872
41391 ?? Z 0:00.00 (UnityShaderCompi)
41416 ?? Z 0:00.00 (Unity Helper)
42367 ?? Z 0:00.00 (Unity Helper)
45602 s000 S+ 0:00.00 grep --color=auto Unity
same for me but with unity 2019 and 2020. unity randomly may freeze and not respond, the only way to make it work again = force hard reboot macbook via on/off button
hi guys, did anybody make some progress on the issue? I would be happy just to be able to kill Unity without restarting.
Any word from our Unity overlords?
Chiming in, been having the same sort of weird hanging issues in Catalina + Unity 2019, I’m currently on 2019.3.10f1 and it still happens. For me it’s always (and only) when I’m working in the animator view but other than that it seems kind of random, it just comes out of nowhere but I know to start expecting it as soon as I open the animator view.
Symptoms are the same as described by others; I have to force shutdown Unity and it disappears from the dock but then my Activity Monitor can’t be used (it just hangs when opening it) and I can see some Unity processes (checking from terminal) that can’t be killed.
The only way to come back from this state that I’ve found is reboot. Makes it practically impossible for me to work on any mecanim animators as it always hangs the whole machine sooner or later (usually sooner)
edit has anyone submitted a bug yet? I’m going to open one later if not, as this is driving me nuts and I’m at a point with my project where I actually need to work on some animators…
I have the same problem with and it almost always happens when the animator window is open, sometimes in the background, but mostly when I am working on it.
Is there a bug report or shall I submit one
edit has anyone submitted a bug yet? I’m going to open one later if not, as this is driving me nuts and I’m at a point with my project where I actually need to work on some animators…
I submitted a bug describing this. Frustratingly, Unity’s bug response email says “please do not share this link with anyone else”.
(I’m also using JetBrains Rider 2020.1 - is the consensus that that’s required to trigger this? Is anyone who sees this bug not using Rider?)
In case this helps anyone - if Force Quit on the Unity process hangs (as described in this thread), I found that if I also force quite a process called ‘debugserver’, Unity would close properly. If you run into this issue, check Activity Monitor to see if you have a ‘debugserver’ process running and try killing that.
I think it’s a consensus, all of us are using Rider with MacOSX.
It happened already on prior versions btw… Not sure if it happened on Mojave but it did sure happen on previous versions of Rider and Unity.
It doesn’t necessarily happens just with the Animator, as someone said on the thread it happens too while debugging quite often.
(I didn’t submit any report btw)
If I remember well, the Activity monitor is not working when this happens, when trying to access it doesn’t work… At least I think I remember that happened and someone in the thread mentioned that too…
Anyway I will try.
@pistoleta - You’re correct that the Activity Monitor doesn’t work for killing the Unity process itself (in my case, shows as pink and won’t dismiss, even after being force quit). My suggestion was to also kill the ‘debugserver’ process (which has no obvious connection to Rider or Unity), if you see it. Killing that process ‘released’ the Unity process, and it was finally able to quit, despite the fact that I was not able to kill the Unity process previously.
I just thought of something my HDD is formatted as APFS could this be the problem, does everyone here has the same format or not??
I was thinking of reinstalling the whole system again, and changing the HDD formatting but wanted to make sure that everyone having the problem have the same format, before I reinstall the whole system.
@theakdev - I’m very skeptical that would make a difference (this issue is almost certainly to do with a debugger process; APFS is well-tested, and if it caused OS soft locks there would be massive outcry from both Mac and iOS users!)
It’s great to eliminate variables, but in this case the hassle to you would be pretty enormous, and almost certainly wouldn’t be worth your time
