Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.2.0b2
2021.1
Issue ID
1280961
Regression
No
Changing the Profiler Frame Count size doesn't affect the data loading time when loading from a file
How to reproduce:
1. Open the attached project (case-1280961.zip)
2. Open the Profiler window (Window -> Analysis -> Profiler)
3. Enable 'Deep Profile' (just to make the issue easier to reproduce)
4. Enter Play Mode and exit it when the Profiler records more than 2000 frames
5. Save the profiling data to a file
6. Load the newly created data file to the Profiler and time it
7. Change the Profiler Frame Count to 300 (Edit -> Preferences -> Analysis -> Profiler)
8. Load the data file to the Profiler again and time it
Expected result: since only 300 frames are being shown, it takes less time to load the data from the file
Actual result: it takes the same time to load
Reproducible with: 2019.4.12f1, 2020.1.6f1, 2020.2.0b5, 2021.1.0a1
Could not test with: 2018.4.27f1 (changing Frame Count size not introduced)
Notes:
Increasing the Frame Count size when the data is already loaded does not reveal the hidden frames
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
Resolution Note:
Team resolution is to close the performance optimization issue by design as this contributes to a feature request, which we need to address anyway as a part of scalability initiative