Search Issue Tracker
Duplicate
Votes
0
Found in
2019.4
2020.3
2021.2
2021.2.5f1
2022.1
Issue ID
1389342
Regression
No
Package Manager takes a long time to refresh when opened for the first time after opening a project
How to reproduce:
1. Create and open a new Unity project
2. Open Package Manager (Notice it takes quite some time to refresh)
3. Close and reopen the project
4. Instead of waiting for the refresh to finish, close the Package Manager window
5. Reopen Package Manager (Notice it took less than a second to show the packages)
Expected result: The Package Manager loads quickly the first time
Actual result: The Package Manager takes some time to load the first time
Reproducible with: 2019.4.34f1, 2020.3.25f1, 2021.2.7f1, 2022.1.0b2
Note:
- On 2022.1.0b2 the initial refresh is fast (step 2) but after following the rest of the steps, it's slow to refresh after opening the project again
- On average, it takes about 9 seconds for the first refresh (depends on the project), but when closing and reopening the Package Manager it takes just 1 second
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #1350368