Search Issue Tracker
Duplicate
Duplicate in 2019.3.X
Votes
2
Found in
2019.3.0a1
2019.3.0a8
Issue ID
1171423
Regression
Yes
AssetDatabase.Refresh() executes slower when compared to previous versions
How to reproduce:
1. Open the attached project("AssetImportPerformance")
2. Go to BugReport > Create 100 assets
3. Observe console
Expected result: AssetDatabase.Refresh takes around the same amount of time regardless of Unity versions
Actual result: AssetDatabase.Refresh takes more time than in previous versions
Reproducible with: 2019.3.0a1, 2019.3.0a11
Not reproducible with: 2017.4.30f1, 2018.4.5f1, 2019.1.12f1, 2019.2.0b10
Note:
- It seems to reproduce only on HDD hard drives. Storing project in SSD hard drive results in expected behaviour even in 2019.3.0a1 and above.
-
triangle4studios
Aug 28, 2020 22:31
Yeah this is insane. 10x Slower than 2019 and I cant revert my project.
-
accitio
Aug 20, 2020 07:39
I'm experiencing this issue in 2020.1.0f1 too - slows me down a lot. Will this bug be reopened or is there already a follow up ticket so that we can track the status of this issue?
-
darthdeus
Aug 16, 2020 19:18
Also still having this issue in 2020.1.2f1 ... it's infuriating how this locks up the editor for such a long time. I'm almost tempted to just downgrade everything to an ancient version just to avoid this.
-
prollings
Aug 03, 2020 14:27
Using version 2020.1 and having this issue. Importing anything or changing a script locks up Unity for a long time.
-
Madalaski
Jul 27, 2020 00:54
How is this a duplicate? This hasn't been fixed in 2020.1!
-
Fernando-Ferreira
Jul 25, 2020 02:33
Unity 2020.1 still having this issue
-
phanemy
Oct 31, 2019 09:12
I find this kind of behaviour too, my custom importer for 3Dtiles files, importing one big file take 3 minutes with version 1, now with the new version it take 18 min
-
Peter77
Jul 24, 2019 12:43
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
- Assertion triggered when using Compile and show code button in Shader inspector
- Wrong elements are selected when holding shift and selecting Game Objects in the Scene Hierarchy
- "Unknown managed type referenced" error is thrown on Play Mode enter with Profiler recording
- CapsuleCast won't detect a hit with a mesh, if the direction happens to be along a face
- ShaderUtil.GetShaderData(shader).SubshaderCount does not count unsupported subshader
This is a duplicate of issue #1171344