Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Fixed in 2018.1.X, 2018.2.X
Votes
0
Found in
2017.3.0f3
Issue ID
986155
Regression
No
[Mac OS]Setting a propery without a backing field crashes Unity
Steps to reproduce:
1. Open attached project "crashtest1"
2. Open test Scene
3. Enter Play mode
Expected result: Unity throws an error and recovers
Actual result: Unity unexpectedly quits
Note: this is reproducible on Mac OS. Running the same code on Windows will result in a proper Console Error.
Reproduced on: 5.6.5f1, 2017.1.0f3, 2017.3.0f3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
Add comment