in 2020.1.23 bug "Invalid AABB a" after open project exist

I had a SkinnedMeshRenderer with Bounds (Center and Extents) set to NaN, Infinity and -Infinity. Resetting these fields to actual valid numbers made the error go away

For what it's worth, I experienced the error "UNITY Invalid AABB a" when I was trying to dynamically change localPosition of Content beyond the verticalNormalizedPosition of a ScrollRect of a ScrollView. In other words if you have a hierarchy of Canvas -> Scroll View -> Viewport -> Content. If you try to move that Content beyond the boundaries of the Scroll View, then the localPosition of the Content may contain values of NaN, and then throw the aforementioned error. To avoid this, prior to moving the Content, temporarily set verticalNormalizedPosition to either 0 or 1. Those are the boundaries of the Scroll View. When set to 0 or 1, check the resulting localPosition of the Content. Were you going to try to move the content beyond the value of that localPosition? If yes, that means you were about to experience the aforementioned error.

unity 5.6 have this bug

Also started getting a flood of AABB invalid errors related to adding a Trail Renderer to moving object (fast moving, fast turning).

The Trail Renderer has the particle/additive (soft) shader attached to it.

although this is an old post, everywhere I've gotten these errors there is a NaN value in a float or double.
Regards

1000+ of the above errors in 5.3.1 in a math asteroids kind of game but not a single one in last iteration of Unity.
Collisions seemed to set it off. No obvious problems with transforms, scale, colliders. etc. Performance seems fine. Went back to 5.3.0f4. Spent a 1/2 day looking for issue

Waiting with baited breath for patch, or next release. Thanks

Hey guys. I fixed this by updating the Unity 3.1.3p3 patch

Problem is seriously effects performance. But if you Build and then Run the game, there seems to be no problem at all. It runs smooth and fine.

i still get this after applying the patch 5.3.1p1 , it looks like that the spamming (thanks who ever fixed it) was turned off but the error still pops up serval times in console.

This is really top priority to fix imo because using a patchversion has many backdraws, no webplayer ect