I am running unity 2017.3.1f1 and I am frequently experiencing editor lockups that have almost no detail about why.
First note, this is not a stack overflow issue. The memory usage does not continue to grow, nor does the editor crash at any point… even if left running for days. It seems to happily be waiting for something to finish that never will.
I am able to attach the debugger to the editor process and hit the pause button, at which point I am being told that the place that is looping around is not managed. I set out to identify which non-managed section might be causing my hangup.
After working the settings for visual studio a bit, I am finally able to hit pause while attached and see that the editor’s main thread is blocked at ntdll.dll!NtWaitForSingleObject(). Seems like the editor is blocking while waiting for something to close down.
Here is the call stack for my main thread:
Last thing the editor attempted to do was unload the domain. Any ideas on what might be causing this issue? Also, any advice on debugging this would be super helpful. My team has suffered a great deal of time having to constantly shut the editor down every second or third play session and I want to get to the bottom of this!
Though this is hard for me to do while being productive in my own environment, I am going to focus on getting a 100% repro case for this and try to shed light on the situation. I should note that my project is VR-related, and uses an unmanaged steam wrapper, and several third party asset store plugins. Please help if you are able… let’s get to the bottom of this time[money] killing unity issue