Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
0.32.0-preview.55
Issue ID
1315817
Regression
No
[Tiny] Develop/Debug Build crashes when NativeArray is disposed inside of Entities.ForEach lambda
Reproduction steps:
1. Open the attached "case_1315817.zip" project and scene01 scene
2. In the Project window, select build asset
3. In the Inspector, set Develop as Build Configuration
4. Select Build and Run and observe the build once it is launched
Expected result: Build does not crash
Actual result: Build crashes
Reproducible with: 0.32.0-preview.55 (2020.2.0b9, 2020.2.2f1, 2021.1.0a1, 2021.1.0a5)
Could not test with: 0.31.0-preview.26 (could not add Dots Runtime Build Profile), 2018.4.32f1, 2019.4.22f1, 2020.2.0b8 (could not downgrade), 2020.2.3f1, 2020.3.0f1, 2021.1.0a6, 2021.1.0b11, 2021.2.0a8 (see notes for reasoning)
Notes:
1. Not reproducible when Build Configuration is set to Release
2. Not reproducible when NativeArray is not disposed
3. Not reproducible when Enable Burst is disabled
4. Error that appears in the Console after the crash:
Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at DataSystem.<>c__DisplayClass_OnUpdate_LambdaJob0.RunWithoutJobSystem(ArchetypeChunkIterator* archetypeChunkIterator, Void* jobData)
at Unity.Entities.InternalCompilerInterface.RunJobChunk[T](T& jobData, EntityQuery query, JobChunkRunWithoutJobSystemDelegate functionPointer)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Tiny development is currently paused