Search Issue Tracker
Fixed in 2018.1.X
Won't Fix in 5.6.X
Not Reproducible in 2017.1.X
Votes
1
Found in
5.6.1p1
Issue ID
965225
Regression
Yes
Performance - Refresh() takes much longer in 2018.1
Steps to reproduce:
1. Open attached project
2. Go into play mode
-After 5000 iterations of AssetDatabase.Refresh() elapsed time will appear in console
Problem: AssetDatabase.Refresh() takes much longer time to execute in 5.4.5p1 and up
Expected result: execution time of AssetDatabase.Refresh() should be the same as it was in 5.4.5f1 or lower
Reproduced on: 5.4.5p1, 5.4.5p2, 5.6.4p1, 2017.1.2p2, 2018.1.0a3
Didn't reproduce on: 5.4.1f1, 5.4.5f1
Tests:
5.4.1f1 - 5.6s
5.4.5f1 - 4.9s
5.4.5p1 - 164.49s
5.4.5p2 - 158.77s
5.6.4p1 - 194.22s
2017.1.2p2 - 222.95s
2018.1.0a3 - 630.30s
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Incorrect ScrollToItem behavior when called on a deattached ListView
- Zooming in/out in Scene View window on the display the zoom takes place in does not work
- Changing Game View resolution when there are 2 Game View Windows on 2 different displays makes the view stretched
- Maximising Game view window on one display makes black bars appear on another display
- Creating a 3D Object when using 2 monitors and 2 Game View Windows on different monitors the created 3D Object only appears on one of them
Add comment