wave8-dynamic-buffer-invalidation

A DynamicBuffer reference crashes after structural changes because Unity DOTS invalidates the underlying chunk memory pointer. Operations like AddComponent, RemoveComponent, or DestroyEntity move data, making the old buffer reference unsafe to read.

To safely read a DynamicBuffer before structural changes, read all required buffer contents first before calling AddComponent or RemoveComponent. Treat buffer references as frame-scoped and never use the old reference after the mutation occurs.

Yes, using EntityCommandBuffer to defer structural changes keeps DynamicBuffer access safe. By delaying AddComponent or DestroyEntity operations until ECB playback, you ensure buffer reads complete before the underlying chunk memory is invalidated.

You need to re-fetch a DynamicBuffer in Unity ECS after any structural mutation occurs in the same system update. If you perform CreateEntity or DestroyEntity and still need buffer data, explicitly get the buffer again to retrieve a valid memory pointer.

The correct ordering for DynamicBuffer reads and structural changes requires reading buffer data before executing mutations. Always perform buffer reads first, then apply structural changes, or defer them via EntityCommandBuffer to prevent undefined behavior.