I don’t have recursive while or anything loop like that.
Because crash does not happen 100% always. But very often like 1/10 or 1/2 chance it occurs.
Why? Very stressful.
Hit enter playmode, then unity crash.
code revision and hit unity editor for recompile, then unity crash.
1, 2 happens as well.
I searched everything on google, but nothing helps.
I am using unity 2021.1.16f1, collaborate.
Did you check the editor logs? Or the crash logs? Might be info there.
Also, often the word “crash” is used to mean “freeze” or “locks up” i.e. the Editor no longer responds to any input. The fact that you mention recursive code and loops make me suspect you mean “freeze” and not a “crash” with exceptions etc.
This is often caused your own scripts. No Google search is going to give you an answer; you need to narrow it down.
Create an empty project and add a few scripts and try the same. If it doesn’t have the same problem then go back to your project and see if the problem start again. Try copying the package manifest to a new project so you’re using identical packages and see if you get the same etc.
Also, assuming your project is backed up, come out of Unity, delete the Library/Obs/Logs folders and reload your project and try again.
I mean crash, that when unity actually turned off with red exclamation mark pop up window, and follow-up pop up that report bug window.
About other options you proposed, copying package manifest, I don’t know how to do this exactly, where is package manifest file? just copy that one file to new project is ok?
About delete Library/Obs/Logs folders, I have did deleting Library folder and it does not work well, so I just download whole asset from collaborate server at new project, but that also same crash phenomenon, so not helped,
and where is Obs folder? You mean “obj” folder? Anyway, delete obj, logs folders, I will try it.
The suggestion was just to test with a new/empty project. Does it do the same thing?
Of course new fresh project won’t crash, but is it issue now? My project here is over 50gb, totally different with empty new project.
So then where is meaning with test with new project?
Great! So you need to determine why your project is different, and why it is crashing, as suggested. It is something in your project and likely not a Unity bug. It may be a bit of trial and error, you want to add the same components one at a time to the empty project to see where it starts to crash. Can you revert to an earlier version via source control or a backup that didn’t crash and look for differences?
you kidding me… I said 50gb… assets only 17gb… scripts are hundreds… packages inside are dozens…
you mean add one asset from my project to new project and find out?
It will take 10 years.
Just revert to a recent backup that didn’t crash, and look for the differences. Use a binary search technique, you should be able to narrow it down in a matter of hours.
Well I would start with what has changed since the last time it worked.
…
This is one of the reasons I like version control. Do you use version control?
You can go back revision by revision until you get to one that works. Now you know the problem was introduced in one of the changes from there. Look at those files specifically.
If you’re crashing then you’ll get a log about the crash which will help you narrow it down. These are attached to the bug report by default BTW.
It happens with all large projects after a while.
You will alt-tab in from VS after changing maybe two characters, and it’ll never be able to compile. If you end the process and re-open the project it’ll work. There is no script error.
I reported one recently, although it’s happened tons of times before and since. Case 1336294.