Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.41f1
6000.0.15f1
7000.0.0a1
Issue ID
UUM-77971
Regression
No
Users are able to change Package and Asset cache Preferences whilst Installations are ongoing
*Steps to reproduce:*
# Create or open any Project
# Navigate to Window > Package Manager
# Navigate to Edit > Preferences > Package Manager
# In the Package Manager Window, start installing a Package, e.g. "2D Sprite"
# Whilst the installation starts, in Package Manager Preferences change the location of "Packages":"Cache Location" to something else than default
*Actual results:* Various errors will be presented to the user depending on the Package, with "2D Sprite", "TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations" Errors are spammed and cannot be stopped. Sometimes some Settings are not created for Packages and other Errors are present
*Expected results:* Changing the location of Package Cache and Asset Cache shouldn't be available to users whilst Package or Asset installations are ongoing
*Reproducible with versions:* 2022.3.41f1, 6000.0.15f1
*Can’t test with versions:* 2021.3.41f1 (No Package Cache Preferences)
*Tested on (OS):* Windows 11
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Resolution Note:
After investigating this issue, we decided that we won't fix it. It is acceptable for users to change the cache location during the download process (the period between clicking the install button and right before the small pop-up installing window). The installation will automatically take the new location into account during which the cache location cannot be altered. The console errors we're seeing are a result of frequent changes to the cache location, which lead to difficulties in locating already installed packages. Therefore, addressing this issue alone won't eliminate those errors.