Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X
Votes
0
Found in
2019.3.10f1
2019.4.1f1
Issue ID
1257929
Regression
Yes
'Verify Saving Assets' option causes a NullReferenceException to be thrown when saving certain Assets
How to reproduce:
1. Create a new Unity project
2. In the Preferences make sure 'Verify Saving Assets' is enabled
3. Create a Timeline asset
4. Tweak its framerate and select File > Save
5. Click any of the buttons in the saving pop-up to close the window
Expected result: no errors are thrown in the Console window
Actual result: a NullReferenceException is thrown
Reproducible with: 2019.3.10f1, 2019.4.2f1
Not reproducible with: 2018.4.24f1, 2019.3.9f1, 2020.1.0a1, 2020.1.0b14, 2020.2.0a15
Notes:
Tested on macOS
In 2018.4 unfreed allocation messages are thrown instead
Add comment
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
Resolution Note (fix version 2019.4):
Fixed in 2019.4.19f1