managed-component-bridge

Store GameObject and MonoBehaviour references on ECS entities using class-based IComponentData to bridge ECS logic with Unity managed objects during hybrid initialization, ensuring the initialization system self-disables after wiring references.

No, managed components require non-Burst access to prevent Burst safety violations, meaning you must isolate class-based IComponentData access outside of Burst-compiled systems to avoid runtime errors.

The best way to handle Unity UI objects during ECS hybrid initialization is storing them as managed references on entities via class-based IComponentData, using a self-disabling initialization system to prevent hot-path performance degradation.

Storing managed references causes GC pressure because class-based IComponentData allocates on the managed heap, which is why this pattern is restricted to one-time setup and kept off hot paths to avoid performance issues.

You should not use managed components in Unity ECS for hot-path logic or Burst-compiled systems, as class-based IComponentData introduces GC overhead and violates Burst safety constraints during frequent runtime updates.

Managed-component-bridge works exclusively for one-time hybrid initialization setup, utilizing a self-disabling initialization system to ensure managed references do not persist into continuous ECS update loops and cause GC pressure.