Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.4.X
Votes
3
Found in
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
2019.3.0a10
Issue ID
1172987
Regression
No
Using stackalloc causes a hard crash with stack buffer overflow exception code
How to reproduce:
1. Open the attached "TestCrash.zip" project
2. Open scene "SampleScene"
3. Enter Play mode
Results: The Editor crashes and the bug reporter does not appear
Reproducible with: 2018.4.5f1, 2019.1.14f1, 2019.2.1f1, 2019.3.0a11
Note: Could not test with the 2017.4 branch since the code uses features that are not part of the C# 6.0 language specification
-
Enverex
Nov 10, 2020 09:40
Not sure why this has been closed, also can't vote for that reason. The issue was logged against 2018 and 2019 but the fix has only been listed for 2018 and 2020. Any reason why 2019 (which has a current LTS) has been ignored?
-
ohzee
Nov 10, 2020 08:49
This bugfix is sadly not fixed on 2019.4 which blocks progress on a project that has to stay on that version of Unity, possible if this can be backported?
-
Frooxius
Sep 28, 2020 19:59
Are the plans to backport this to 2019.4? I have a project that's affected by this and even using 2019.4.11f1 will result in a crash.
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2020.1):
Fix crash that may occur when using stackalloc.