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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Add comment