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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment