Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a1
2018.3.0b4
Issue ID
1088897
Regression
Yes
Crash on memset when passing integer instead of array to NativeArray constructor in subthread
How to reproduce:
1. Open the attached project
2. Open the "Main.unity" scene
3. Press Play
4. If Unity didn't crash, wait a bit
Actual result: Unity crashes.
Reproducible with: 2019.1.0a9, 2018.3.0b10, 2018.3.0a1.
Regression introduced in: 2018.3.0a1.
Not reproducible with: 2018.2.16f1, 2018.1.9f2, 2017.4.15f1
Notes:
The crash happens because NativeArray<T0>(T[] array, Unity.Collections.Allocator allocator); constructor gets an integer instead of an array.
The crash is not reproducible outside of subthread.
Error is thrown before the crash:
Assertion failed on expression: 'gCurrentManagedTempMem != NULL'
--------------------------------------------------------------
Fixed in 2019.1.0a12, 2018.3.0b13.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [HDRP] Recursive rendering refraction is very different compared to Rasterization/PathTracing
- [VFX] SMR sampling first frame after culling in T-Pose
- Can't select color from Editor with color picker when Unity Editor is on Secondary monitor
- [Linux] "Error while reading movie" errors in Learning templates due to unsupported .mov video format
- [Android] Crash with Signal 11 when opening app from floating icon state
Add comment