Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0f3
Issue ID
897134
Regression
Yes
[Mac] Debugger corrupts vector2 values
Repro steps:
1. Open the provided scene
2. Open the script
3. Press the "Play" button in MonoDevelop
4. Add a breakpoint on line 10 (where the vector2 is declared)
5. Enter play mode in Unity
6. Press the "Step over" button in MonoDevelop
7. Hover over the "v" in "Vector2 v =..." until a menu pops up
8. Expand the pop up menu
9. See that the values have changed to nonsense
Expected: to see the same values as declared before.
Actual: the values have changed drastically
Reproduced with: 2017.1.0a6, 5.6.0f3, 5.5.3f3
Working with: 5.4.5f1 (regression here)
Bug only happens on a mac
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment