Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.2f1
Issue ID
935340
Regression
No
"Assertion failed: Invalid AABB a" error appears after multiple object collision
Steps to reproduce:
1. Download PhysicsCrashRepro.zip and open "CrashScene" scene
2. Enter Play mode
3. Hold A to spawn objects
4. After 10-20 seconds game objects disappear and "Assertion failed: Invalid AABB a" error show up
Results: Console starts spawning error "Assertion failed: Invalid AABB a" and most of the spawned game object position is set to NaN
Reproduced with: 2017.3.0a5, 2017.2.0b8, 2017.1.0p4, 5.6.3p1, 5.5.4p3
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
MrDude
Feb 04, 2019 22:43
Oh wow... I thought CJBRUCE posted this 2 weeks ago... Didn't notice the year :P Sorry for necro posting. I see the bug was fixed a long time ago. Glad to hear.
This makes it rather mysterious then that I am the only one who is still getting an average 350 errors per second in Unity 2018.3.6f1 when they fixed this bug so long ago. :(
Just my luck :(
MrDude
Feb 04, 2019 22:35
Well this is disappointing.... :(
I am using a Unty demo project in 2018.2.6f1 and getting on average 22,000 errors per minute:
"In valid AABB a"
"Invalid localAABB. Object transform is corrupt"
"Invalid worldAABB. Object is too large or far away from world origin"
...but they have already been marked this ticket as "Wont fix".
Nothing to do but live with it then, I suppose... :(
cjbruce
Jan 24, 2018 03:41
I am seeing the same issue. I understand that this is a difficult to resolve, as it appears to result from the process of physics collision resolution. Are there any recommended workarounds to this issue? Perhaps by saving the state of physics objects prior to the collision, and placing the objects back to this prior state?