Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
0
Found in
2020.3.48f1
Issue ID
UUM-44194
Regression
No
Time.realTimeSinceStartup returns wrong values when using OnDestroy()
How to reproduce:
1. Download and open the attached "RealTimeSinceStartup" project
2. Enter Play mode
3. Wait a couple of seconds before exiting Play mode
4. Observe the console window
Expected outcome: OnDestroy() returns a value of a couple of seconds (similar to OnApplicationQuit())
Actual outcome: OnDestroy() returns a value lower than a second
Reproducible with: 2020.3.48f1, 2021.3.29f1, 2022.3.6f1, 2023.1.7f1, 2023.2.0b3
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
- Console shows Exception: {"error":"not found","detail":["not found"]} after opening Build History window
- [HDRP] Volumetric cloud shadows disappear when there is no directional light shadows
- “Selector” column names in the Search window are lowercase when added
- Install List Project Counter Panel can be right clicked through and Install Context Menu can be opened disabling Project Counter Panel's buttons
- [MacOS] Scene is marked/flickering as dirty (with asterisk) when dragging a Material on a GameObject in Scene view
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2020.3.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.