My team and I recently upgraded from 2017.1 to 2018.3 and the game started crashing often.
We even got some kind of reproduceability where we can know it’s going to crash after some steps, but there is no specific trigger.
The closest thing to an “answer” I’ve found is a stack trace out of an editor crash:
========== OUTPUTTING STACK TRACE ==================
Experiencing the same crash in one of my projects in 2019.1.4f1
Seems to happen only when objects with rigidbodies that have had some kind of force applied to them get disabled or destroyed. Seems like the physics engine is still trying to access these objects on the frame after they are destroyed for some reason.
I filed a bug report which I got a response from @evelinastaniulyte redirecting me to an existing bug report that says it has been fixed in 2019.3. I replied to the email asking if we can expect this same fix to also be rolled out to earlier 2019.x versions (2019.1 and 2019.2 since they both have the problem as well) and have not received a confirmation.
Awaiting more info, would really like to get an update on this as we don’t feel comfortable upgrading the project to 2019.3 since it has not been released yet, but this issue is 100% reproducible in our game. And the only way to prevent the crash for us, is to not ever apply physics to our rigidbodies, which obviously is a pretty major road block.