Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.1.1f1
Issue ID
964848
Regression
No
Crash on ves_icall_InternalInvoke when Activator.CreateInstance() method is called
How to reproduce:
1. Open attached Unity project "JsonParserExtended"
2. Load scene "Test"
3. Enter Play mode
Expected result: Unity should not crash.
Actual result: Unity crashes on [c:\buildslave\mono\build\mono\metadata\icall.c:2735] ves_icall_InternalInvoke.
Reproducible with: 2018.1.0a3, 2017.3.0b9, 2017.2.0p2, 2017.1.2p2, 5.6.4p2, 5.5.5p1.
Notes:
* Crash is invoked by JsonParserExtended.cs script (line 46).
* Crash occurs only when index of the object in Activator.CreateInstance() method is 1. Other indexes are not causing crashes.
Fixed in: 2018.1.0b2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "The name 'Unwrapping' does not exist in the current context" is thrown when using Unwrapping.GeneratePerTriangleUV in the Build
- The "Add Component" context menu root level has a parent when is reopened after selecting a Component
- [Android] Crash on memcpy when building for Android Platform
- Cannot create DropdownField with nested choices when using UIToolkit
- Lightmaps are baked incorrectly for GameObjects when their Position is <=-2048 or >=2048 on any of the coordinates
Add comment