Search Issue Tracker
By Design
Votes
0
Found in
2023.2.0a1
Issue ID
UUM-30141
Regression
No
NativeArray IsCreated returns true for objects that are disposed
How to reproduce:
1. Download and open the attached project
2. Enter "Play" mode
3. Observe the console window
Expected outcome: No errors appear
Actual outcome: "ObjectDisposedException: The Unity.Collections.NativeArray`1[System.Int32] has been deallocated, it is not allowed to access it" error appears
Reproducible with: 2020.3.45f1, 2021.3.18f1, 2022.2.6f1, 2023.1.0b3, 2023.2.0a1
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
This is an intentional design tradeoff.
Native Containers do not support disposal from multiple aliases. These containers aren't reference counted or version tracked outside of the editor. The requested use case would require extra data and logic in standalone player builds which could incur an unnecessary performance penalty.