Hey there,
I am not sure how and it would probably be hard to narrow down, but I have a small scene I have been working on and at the time it had one vehicle entity in it in which was being moved via a job. The vehicle has MeshRenderer, PhysicsShape, and PhysicsBody on it. I had the Physics Settings scene object from the Sample scene as well as the mouse interaction script. I had started the scene, spawned a vehicle and was just letting it roam around as I wanted to see how things would turn out after a while because I noticed when I had multiple vehicles, after a minute or so they would all start to nose dive at the same angle through the single ground plane collider I had as a floor.
I started it up, but my wife needed my help with something so I paused it and headed up stairs, had dinner and had sat back down at the PC and had forgotten about it until the PC started to bug out, I looked at my memory usage and it was at 99-100%. I tried to catch the stop button in time, but the PC killed my user session before I could.
I mostly just wanted to report the incident so that it was known. I am pretty sure it was because of the recent addition of physics to my project, as I let my system run with 50,000 vehicles for an hour the other day just to see how it would react and see if anything ended up bugging out and it held fine the whole time without any memory leaks or anything and I just added in the physics package and the few physics objects to my scene either yesterday or last night.
Usually, I disable or better take out bunches of game objects that doesn´t trigger the bug until I get with one game object or component that trigger the bug. It can be as for example a join component with new parameters. Sometimes is difficult to debug some problems when take time. But is the only way I found to be sure before making a bug report. If you make a difference between projects you can look if some components parameters have changed and exclude does that are the same.
Oh, I am with you, I am just more surprised that this occurred while everything the editor was paused. I tested after it happened to make sure systems were paused when the editor was and it certainly didn’t look like they should have still been running, but I don’t know exactly what ends up happening behind the scenes.
