Search Issue Tracker
Fixed in 0.10.0
Votes
3
Found in [Package]
0.4.0-preview.10, 0.6.0-preview.24
Issue ID
1207875
Regression
No
[ECS] Internal native array is deallocated when ComponentDataFromEntity is captured into 2 lambda jobs
How to reproduce:
1. Open the attached project ("case_1207875-NativeArray.zip")
2. Open Test Runner
3. Run the 'CdfeCaptureSharing' test
Expected results: Test succeeds
Actual results: Test fails with "System.InvalidOperationException : The NativeArray has been deallocated, it is not allowed to access it" error
Reproducible with: 2019.3.3f1, 2020.1.0a24
Couldn't test with 2017.4, 2018.4 (package is not supported)
Reproducible with package versions: 0.4.0-preview.10, 0.6.0-preview.24
Note:
On 2020.1 stream, the test fails with "System.InvalidOperationException : The UNKNOWN_OBJECT_TYPE has been deallocated, it is not allowed to access it" error
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note (fix version 0.10.0):
The issue here is that all existing ComponentDataFromEntity objects are invalidated when a structural change occurs. In this case, SimpleCdfe is invalidated by the RemoveComponent command played back by ecb.Playback(). SimpleCdfe2, if uncommented, is created after the ECB playback, so it would still be valid in the second ForEach loop.
The error message for this was awful for a long time, as you noticed (what NativeArray? What deallocation?). I'm happy to report that in 2020.1 + Entities 0.10.0 the error message is much more explicit and actionable (it would be something like "The ComponentDataFromEntity has been invalidated by a structural change".