Bug [Fixed] (Case 1115073) References to Native Objects that do not make sense

I think this might be the same issue as 987839, but that was reported using the older API, not using the new memory profiler, so I would not call this as a duplicate. See more info at https://forum.unity.com/threads/wip...analyzer-for-unity.527949/page-2#post-3619123

However, I doubt this is really By Design, even though the older issue was closed with this resolution.

We are getting references (like 1000+ references) to every terrain Mesh, even thought the objects that allegedly reference it are GUI objects etc.; you can find the one real reference (MeshCollider) between the references as well, but the rest are nonsense and should not be referencing the Mesh.

I have uploaded a snapshot from a real project where you can check these wrong references with the bug report; you can find it as Case 1115073.

 

Thanks!

Yeah, I guess either of those is a fair game; having at least an understanding why it acts that way would be nice, but proper fix would be better (unless Unity really references native object between each other in the most befuddling ways).

 

Have you heard back from them yet?

 

Well, it seems they just auto closed the issue and I missed the email, because I did not provide a repro, just the snapshot. I will try to get it reopened, because this issue is really really annoying. :/

 

It unfortunately it doesn't seem to sound like the problem I've seen, where a Mesh has references to an AudioSource for example. Or could it be same as well?

Thanks for the quick reply!

 

Thanks again for rapid reply.

I hope it's the same issue. With this issue getting fixed, it could also boost profiler performance! If there is no need to transfer and evaluate 509.117.918 connections, but only a fraction, that could be a huge performance and memory win.