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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Add comment