Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.0f3
Issue ID
974947
Regression
No
Attempt to inspect a local variable during debugging session results in Unity Editor crash
How to reproduce:
1. Open Unity
2. Load user-submitted project (daycycle-goap.zip)
3. Open "Example1" and "Example1A" scenes additively
4. Open "AStar.cs" in Visual Studio
5. Put a breakpoint in line 33
6. Start debugging session attached to Unity Editor
7. Expand "node" variable in "Locals"(local variables window)
Expected result: Variable is expanded showing its internal variables
Actual result: Unity Editor crashes and debugging session is stopped
Reproducible with - 2017.1.0b3, 2017.1.3p1, 2017.2.1p3, 2017.3.1f1, 2018.1.0b1
Could not test with - 5.6.5p1, 2017.1.0a1(Project is not compatible), 2018.1.0b5 (Visual Studio Tools for Unity doesn't support these beta versions yet)
Does not reproduce on Scripting Runtime Version: .NET 4.x
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
- Unity Version Control server textfield’s text overlaps with the dropdown triangle button in the Explore repositories window when an organization with a long name is selected
Add comment