Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2018.2.0a1
2018.4
2019.2
2019.3
2020.1
2020.1.0a17
Issue ID
1216135
Regression
Yes
Unity freezes when Time.timeScale is set to NaN
How to reproduce:
1. Open attached project "Case_1216135" and load "Scene"
2. Press Play
3. Click Tab on your keyboard
Expected result: Error is thrown in the console
Actual result: Unity freezes
Reproducible with: 2018.2.0a1, 2018.4.17f1, 2019.2.20f1, 2019.3.0f6, 2020.1.0a22
Not reproducible with: 2017.4.36f1 (throws error in console)
Notes: In order to get NaN, division 0/0 is used, but as this throws an error, a variable is used as a denominator.
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Resolution Note (fix version 2020.1):
Fixed in: 2020.2.0a12
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.1f1