I have been working on a project for a little while and was spending the last few days polishing it up when I ran into this weird bug: Invalid AABB aabb Appears as a red critical error in the log. I know it's axis-aligned bounding box and relates to the render bounds. I'm just not sure how what I'm doing impacts that. I've been trying various things but can't seem to fix it. A little background: I have a single canvas in my scene which houses all of my ui. The problem initially surfaced when I had a custom graph object with ~5,000 datapoints which had a UILineRenderer (provided in this topic) when I disabled the line, the error floods the log forever and ever. Likewise if I delete the object... I also noticed it in an area where it wasn't showing up before where I'm dynamically adding, then after clicking on a button deleting 30-200 buttons that exist in a grid (with a content size fitter) The only thing in common between the graph and the buttons that are dynamically populated is that they are both prefabs and that they are nested within a huge hierarchy of horizontal/vertical layout components Here's what I have tried so far: Looked at all my ui elements for 0 scale or 0 width/height. I wrote a script too but have not found anything I have tried to narrow down where the problem occurred. I successfully found the UILineRenderer being one cause of the problem (when I make it active and inactive, the error outputs once to the log) but it's not entirely clear it is just the UILineRenderer since a test-project doesn't do it. The button issue I'm still clueless on as I didn't notice it before I tried moving the assets and scene to a new project; the issue still occurs Disabling and reenabling the main canvas will usually stop the error from spamming but will void the interactiveness of the ui Scouring the patch notes / release notes for mentions of this bug. At the very least it'd be nice if the name of the offending object was present Someone on one topic mentioned possibly a corrupt scene file...I've thought about recreating the scene but it's huge and that would weeks or even months to do, so it's not really a great option. Does anyone have any ideas? I have not been successful in reproducing it in a sample project to send to Unity. I've been hesitant to upgrade to 5.2 since hearing about all the bugs but does anyone know if 5.2 would fix this bug? I'm currently upgrading to 5.1.3f1 to see if that helps at all.. but not too optimistic. Last question, if I make a build with this bug will my users see problems? Just running through it on my own really quickly had no ill effects... Thanks!