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
- "Objects are trying to be loaded during a domain backup." errors on entering Playmode
- Transform Node does not have outputs when it is created
- Changing the Default Icon does not change the executable's icon when re-building the project
- Texture is stored upside down when using Blit
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
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.