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
- The Editor does not recognize button release when first releasing the "LShift" button and then "Numpad2"
- Reflection Probe doesn't load until it's selected in the Hierarchy window when the project has been opened
- "ArgumentNullException" error in the Console when selecting certain ScriptableObjects and entering Play Mode
- Configurable joints become bouncier when setting "Bounciness" below 1
- Prefabs get corrupted when editing Particle System curves
Resolution Note (fix version 2019.4):
Fixed in 2019.4.19f1