This is been happening to me since i updated my project to Unity 2017, it’s been happening with .1 and now it’s happening with 2017.2.0f3. I have no idea what’s going on and it’s getting really frustrating lately, the only hint i could give is that this only happen after i change a script, save, let it compile and then press play, it don’t always happen though, sometimes it works just fine, sometime it doesn’t, any help please ?
I’ve seen in some threads Unity team asking for the damp file, here is mine created from task manager when the freeze happen.
I believe Unity Technologies would be thankful if you submit this via a bug-report, using their official Bug Reporter tool as described in this document. They don’t really look out for bug-reports in the forum.
Using the bug-reporter seems to be an important step, because it makes sure the report is in Unity Technologies bug-tracking pipeline, has to be processed at some point and you can kind of track if it’s fixed. Using the forum is often used to add to a little more attention to a bug-report, but does not replace submitting the bug-report.
It’s from advantage to attach a project to the bug-report that UT can use to reproduce the issue and test their fix against. Attaching a video to the bug-report that shows how to reproduce the issue and the issue itself, has been proven useful too.
The easier an issue can be reproduced by QA, the more likely it is to get forwarded to a developer, who might or might not work on a bug-fix for that at some point.
After you submitted the bug-report, you receive a confirmation email with a Case number. UT often asks us to post the Case number in the forum thread, which allows them to find that bug-report if they look at your post.
Following these steps will increase the chance that UT is looking at your issue tremendously.