Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.1.20f1
2022.2.0b12
2023.1.0a14
2023.2.0a1
Issue ID
UUM-17560
Regression
No
Error currentFileSystemTime.ticks != 0 thrown while cancelling loading of standalone profiler
How to reproduce:
# Create new project
# Open Standalone Profiler (Windows>Analysis>Standalone Profiler)
# Click cancel button when it becomes available
# Observe console
Error: currentFileSystemTime.ticks != 0 using check file Temp/FSTimeGet-6fa2fceb022564f36bcaea35e32d25d1 =>
Reproduced with: 2022.1.0a13, 2022.1.20f1, 2022.2.0b10, 2023.1.0a15
Does not reproduce with: 2021.3.11f1 (cancel button never becomes clickable)
Note: Tested only on MacOS. Opening standalone profiler again throws the error repeatedly.
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
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
- Building the project for Web with ASTC Texture Compression results in black screen
- “ArgumentException: Object reference not set to an instance of an object” errors are thrown when adding the component with Entity as Key for HashMap
- Visual Effect Model overlays tooltip is left in Scene when unfocusing VFX Node and the overlay dropdown menu is opened
- Unity crashes during the scene template selection in the "Inspector" tab
Resolution Note:
We recognise this as a legitimate problem, but in the spirit of transparency we are closing this issue, because we are not going to be able to provide a fix in a near future.
We understand that this will cause problems for some users, so we may address this in a future version.