I tried to run the project on Units 6000.0.23 LTS, started and stopped after a few seconds, the editor froze for a moment and crashed with an error and a suggestion to send a report, and this is the situation with >= 6000.0.18, so I still use 6000.0.17, which crashes less often (5-10 times/day), it was stable only on 6000.0.10. The editor also crashes with simple actions with objects, when trying to change properties or assign objects to properties in the inspector. I sent a report with logs several times and nothing changed.
I tried to create a clean project, launched the project, created an object, no errors were noticed, I don’t understand what to do. Should I create a new project and transfer everything I created? It looks like there is some incompatibility. I created the project in version 2021 and constantly updated to the new version.
macOS 15.0.1. Unity 6000.0.23.
Hi! Sorry to hear about that! Do happen to have any of the ticket numbers (they start with IN)? So we can look it up internally and see what’s going on? Thanks!
Hi! I sent two reports but did not receive any responses with incident numbers.
Hmm… Is it the Apple crash report that’s showing up? If that’s the case we won’t receive those reports. But the next time the editor crashes relaunch and submit a bug with the Unity Bug Reporter (Help Menu/Report a Bug…), you should get an incident number then. Report it here and we can take a closer look.
In the mean time could you post one of the editor logs from a crash?
Of course I sent at least 2 reports using Unity Bug Reporter and did not get incident number. First report was sent about 2 months ago.
Editor.log.zip (302.7 KB
In my project I use my own implementation of terrain, native containers are used, I guess the problem arises somewhere here. I attached Editor log.
Editor.log.zip (14.7 KB)
Another log
I read the log and understood what was going on. I disabled Resident Drawer in the URP settings and the editor stopped crashing with an error.
Ahh ok. I was just going to suggest something similar. I’m glad that you got it worked out and I’m going to pass this along to the URP team so they can take a deeper look at it.
Sounds like this issue should be fixed in a future release of Unity 6.0 (not sure which specific version at the moment)
hi! am facing the same problem today on 6000.2.2f1, am not an expert I just started leaning.. please how can I fix this??