Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2018.2.0a1
2018.2.0f2
Issue ID
1058992
Regression
Yes
After Unity loads the project it crashes on System.Array:ClearInternal (System.Array,int,int)
How to reproduce:
1. Open user's attached project "ID.zip"
2. After the project is loaded wait from 10 to 15 seconds and the project will crash
Expected result: User can modify the project through Editor
Actual result: Unity crashes
Reproducible with: 2018.2.0f2
Not reproducible with: 2017.2.3p2, 2017.4.7f1, 2018.1.9f1, 2018.3.0a1, 2018.3.0a5
Note: Majority of the time the crash is reproducible. Sometimes to reproduce the crash you will need to close and open the project a few times. I have attached Editor.log, crash.dmp and error.log files in the description below
First three lines of the stack trace:
0x00007FFFCFCD4687 (mono) [f:\dd\vctools\crt_bld\SELF_64_amd64\crt\src\amd64\memset.asm:148] memset
0x000000000073CED4 (Mono JIT Code) (wrapper managed-to-native) System.Array:ClearInternal (System.Array,int,int)
0x000000000073CDC8 (Mono JIT Code) [/Users/builduser/buildslave/mono/build/mcs/class/corlib/System/Array.cs:910] System.Array:Clear (System.Array,int,int)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment