This is caused by user code trampling memory and thus cannot be fixed on our side. Unity.Collections.LowLevel.Unsafe.UnsafeUtility.WriteArrayElementWithStride performs no bounds checking for performance reasons, using it incorrectly can corrupt memory which depending on what gets overwritten may or may not crash Unity Editor.

The issue here is present in TrainingRoom.cs in EndEpisode

```
if (startingPosition != null)
{
//agent.transform.position = startingPosition.position;

//agent.transform.rotation = Quaternion.Euler(0f, Random.Range(-180f, 180f), 0f);
Vector3 newPos = startingPosition.position;
agent.GetComponent<Obi.ObiSoftbody>().Teleport(newPos, Quaternion.identity);
}
```

I haven't dug too much into the actual cause, but the Teleport() triggers Out Of Bound Writes to Native Allocations (Allocated via UnsafeUtility), these Out Of Bound writes are trampling memory and will cause a variety of problems.

The user can see these writes by modifying ObiNativeList.cs and adding a log and early return (to prevent the write trampling memory) to the array index operator e.g. :

```
public T this[int index]
{
get
{
return UnsafeUtility.ReadArrayElementWithStride<T>(m_AlignedPtr, index, m_Stride);
}
set
{
if (index >= m_Capacity)
{
Debug.Log("OOB Write - Ignoring");
return;
}
UnsafeUtility.WriteArrayElementWithStride<T>(m_AlignedPtr, index, m_Stride, value);

if (m_ComputeBuffer != null)
m_ComputeBuffer.SetData(AsNativeArray<T>(), index, index, 1);
}
}
```