Sometimes (every few days) the editor crashes after opening the project. After this initial crash the project has to be fully reimported (which could take hours) by removing the Library folder to fix the issue.
This crash was introduced on Unity 2020.2b1 and has caused a lot of issues for us.
My guess is that when exiting the editor, some code path corrupts the imported assets in Library folder. At first this issue showed itself when opening a few specific scenes but in b2 it just always crashes the editor on startup.
It’s really hard to reproduce it, but makes it really scary to close the project because I may be forced to reimport it all again. Does anyone else has this issue? Maybe there is a solution to this?
The editor crashed again today, which means that this issue still exists in the b5 version. @LeonhardP Here are some of the latest crash dumps. Hope they help.
I have exactly the same issue. Our team has to reimport the whole project every… say 2 days or so. Described symptoms are exactly the same for us. I feel like b3 and b5 happens more often… it is really frustrating indeed. Sometimes it crashes when selecting a prefab in editor… and then…after that we have to reimport… feels like… asset refreshing… detection is corrupting library folder somehow.
Like above said. It is very difficult to pin point what is actually causing this. We are just biting dust and keep dragging on since we are using beta version… but oh man… it is dreaded experience at the moment.
When someone in our team shouts shxt… then we know what happened… and we even laugh at it now… but ofcourse it is a shallow, angry and frustrating laugh…
The problem is that it’s so random and hard to reproduce. One time I opened and closed the project 10 times and it didn’t crash, and then some day after I reopened the project because of a change in Burst compiler version it crashed and had to reimport. I think for us it has to do with the long exit times , I think Unity corrupts the Library files when quitting while trying to do some cleanup.
When Unity normally imports our project, we get a lot of Burst error messages in console. Until now I just ignored them. Maybe it’s some kind of a memory bug in our burst code… But how could it corrupt the Library files so that consecutive imports also would fail? Our burst scripts are all for runtime animation and some physics simulation stuff.
I am currently using 2020.2 beta 8, and this issue is becoming out of hand. Almost every 5 min or 10 mins or so, while trying to compile any changes to the script, it crashes, and then it forces me to delete library folder and reimport the whole project. Today, I have done this like 10 times already.
No, it’s still private. They still haven’t been able to reproduce this issue. Also, our issue is a little bit different: it happens now only while opening the project. And it’s still happening on the newest b8.
I’ve been having a similar problem with 2020.1 and looks like it’s connected to the version check - it has consistently crashed on startup for a few weeks whenever there is a new Unity version available. Disconnecting from the internet fixes it, and afterwards it keeps working even if you reconnect; check if that works for you? I’ve filed a bug which was said to be a duplicate of an existing asset corruption issue, and then emailed my additional observations.
Now that we are moved to 2020.2 we see this also.
We mostly crash in our build machine during asset importing.
Asset importing seems to be the trigger for mahdi looking at the editor.log files.
We also get a useless call stack.
I tried opening the dump file in Visual Studio but I only see a callstack for CaptureContext after the exception is handled, but can’t see what the exception was or where it was.
I can also submit a ton of crash dumps, not sure if it is any help.
