Search Issue Tracker
Active
Votes
0
Found in
2020.3
2020.3.25f1
Issue ID
1398758
Regression
No
Large amount of cache entries cause a cache miss to take more time to complete when using "Caching.IsVersionCached"
How to reproduce:
1. Open the user attached project (CachingMetricsTest.zip)
2. Open the test runner window by going to the menubar: Window -> General -> Test Runner
3. In the "Test Runner" window, change to the "Play Mode" tab
4. Click "Run All"
5. Let the tests run until they complete
6. Open the "Test Report" window by going to the menubar: Window -> Analysis -> Performance Test Report
7. Click on Metrics.IsVersionCached entry
8. Observe the charts under "Sample Group View"
Expected result: As the cache entries grow the "CacheMiss" chart doesn't show any significant change in call time
Actual result: The "CacheMiss" chart shows the increase of time as the cache entries grow
Reproducible with: 2020.3.25f1, 2021.2.10f1, 2022.1.0b6
Couldn't test with: 2022.2.0a3 (Crashed without a stack trace)
Reproducible on: Ubuntu 20.04
Not reproducible on: Windows 10
Notes:
1. Running the tests takes a very long time (up to an hour or more) and the Editor will appear to be frozen during some of that time
2. If the test report graphs don't show up press the "Refresh" button
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment