+ Correction is welcome!

It's mostly can be happened on creating/loading non-GameObject native instance.

In our case, some external asset make this trouble causes memory leak and it's hard to find root causes during profiling memory...

So make sure to free referencing instances on end of life-cycle!

🧵

#unitytips

The solution is make it explicitly assigning null to member on end of life-cycle.

class NI {
...
void OnDestroy() {
if (Child != null)
Child.Parent = null;
Child = null;
}
}

It'll break both of references so GC and asset system can free/unload these instances!

🧵

#unitytips

Here's the reason :

- NI has reference count from it's Child member's instance member, _parent, this causes NI's managed wrapper instance still be alived on memory.
- MI has reference from native instance, NI's member, Child, causes GC cannot sure it's okay to free that instance.

🧵

#unitytips

For example :

class NI : ScriptableObject {
public MI Child;
}

class MI {
public NI Parent;
public MI(NI parent) {
Parent = parent;
}
}

NI asset = ...;
asset.Child = new MI(asset);

This causes cyclic reference so it cannot be freed completely even `Destroy(asset)`.

🧵

#unitytips

You should deserve have some credits that fills entire screen

Yoo it's already feels satisfying

Unity Object is somehow cursed...