Are you referring to this? No. Not yet. I want to - it’s in the backlog.
It comes up only when Resources.LoadAll<Quest>("") is called. InventoryItem loading doesn’t seem to affect it.
If you can load up the console, you’ll also see these in a non-development build of the game. It might be a red herring too but I know spamming the log with errors tends to result in performance drops which could be an explanation why we saw performance gaps loading Quest but not InventoryItems. I haven’t done detailed profiling to be sure.
I started looking deeply at logs in built games after I made a build and wanted to troubleshoot various build-related issues - stutters, performance drops, unexpected null values, etc.
Yeah it does seem like a Unity error, but it is weird that it is triggered by loading Quest and not InventoryItem. I am getting pretty close to refactoring Quest to not have those System.Serializeable objects. That’s my best guess since I remember seeing something Unity and nested/custom Serialized objects. I am “out of time” for this afternoon but will come back to this in the evening.
2022.03.10 - the latest LTS