Search Issue Tracker
By Design
By Design in 2022.2.X
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 <...>"
Comments (1)
-
runevision
May 05, 2026 17:07
If PlayMode is stopped after a readback to NativeArray has been scheduled but before it has completed, how exactly is one supposed to cleanup (dispose) the NativeArray?
The readback never happens if PlayMode has been stopped, so the NativeArray is undisposable indefinitely and prevents cleanup from ever happening - Unity will throw the InvalidOperationException mentioned in the issue description if disposing is attempted.
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 CheckDeviceStatus when converting materials from built-in to URP and using DX12
- Higher CPU frame time on Android devices with Cortex-A510 efficiency cores (vs Cortex-A55)
- Alt+click on List header does not recursively toggle child foldouts when items use a UI Toolkit CustomPropertyDrawer
- Hub Window is closed when closing Unity AI Window via the OS Window Close Button on Windows
- Artifacts are rendered in UITK when using Font Assets and using negative outlines
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.
Resolution Note (2022.2.X):
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.