Search Issue Tracker
By Design
Votes
0
Found in
2018.2.12f1
Issue ID
1091525
Regression
No
Editor crashes with ves_icall_MonoPropertyInfo_get_property_info when stepping over a breakpoint in Visual Studio
How to reproduce:
1. Open attached "10" project
2. Add a breakpoint on line 79 in GameSaver.cs
3. Attach Visual Studio debugger and enter Play Mode
4. Press "Reset" button in the Game View
5. When break point is hit, use Step Over (F10) button in Visual Studio
Expected result: Editor does not crash
Actual result: Editor crashes
Reproduced with: 2018.2.14f1, 2018.3.0b8, 2019.1.0a6
Cannot reproduce with 2017.4 because of compilation errors
Note: Editor does not crash if the breakpoint is deleted
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Actual crash was due to creating incomplete reflection type instances and then using them.