Search Issue Tracker
By Design
Votes
1
Found in
2020.3.32f1
2021.2.16f1
2022.1.0b14
2022.2.0a9
Issue ID
UUM-7340
Regression
No
Array is marked as undisposable when using AsyncGPUReadback.RequestIntoNativeArray
How to reproduce:
1. Open the attached project (NativeArrayTest.zip)
2. Open scene Scenes/TestScene2
3. Press the Play button, then press again to exit Play mode
4. Observe the Console
Expected result: no InvalidOperationException regarding undisposable array is thrown
Actual result: "InvalidOperationException: The Unity.Collections.NativeArray`1\[System.Single] has been set to undisposable and cannot be deallocated. " is thrown
Reproducible with: 2019.4.37f1, 2020.3.32f1, 2021.2.16f1, 2022.1.0b14, 2022.2.0a9
Notes: in 2019.4, the error is "InvalidOperationException: The native container has been set to undisposable and cannot be deallocated.
Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle.CheckDeallocateAndThrow <...>"
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Errors are caused by (1) multiple simultaneous readbacks to the same NativeArray and (2) disposal of NativeArray before a readback to it has completed. Both of these operations are invalid.