Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0f3
Issue ID
949875
Regression
No
Crash on get_generic_context_from_stack_frame when debugging Animator property with Visual Studio Code or MonoDevelop
To reproduce:
1. Download and open attached "Learn Roughlike2D.zip" project.
2. Download and install Visual Studio Code if you do not have it.
3. Install Unity Debugger Extension version 1.2.1 for Visual Studio Code.
4. Open your Unity project folder in the VS Code.
5. Navigate to Assets->Scripts and open Enemy.cs trough VS Code.
6. Set a breakpoint on line 45 "(this.animator.SetTrigger("attack");"
7. Debug your code with Unity attached.
8. Return to Unity editor and enter Play mode.
9. Move player using arrow keys so he would collide with the enemy.
10. When the breakpoint hits, move your mouse cursor on "animator" word in line 45 "this.animator.SetTrigger("attack");" to get know what value it has.
Expected result: VS Code shows what value this line had and after getting back to Unity it is possible to continue working.
Actual result: VS code shows the value of animator and Unity crashes afterwards.
Reproduced with: 2017.3.0b1, 2017.2.0f1, 2017.1.1p2, 5.6.3p3.
Notes: After hovering on "animator" keyword the crash might occur in time interval from 1 to 5 seconds. Crash appears only when trying to debug lines with animator property. Also happens when debugging with MonoDevelop.
======================
Response:
This looks like a bug in in the old Mono run time library code. I wasn't able to reproduce this using the new Mono scripting run time library. As we are moving towards phasing out the old run time and replacing with the new one, we are unable to spend resources on fixing this. Please use the new scripting run time if this bug interferes with your work.
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
Add comment