Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.23.1
2.3.16
Issue ID
ADDR-3868
Regression
No
No Addressable Scenes are unloaded when "Resources.UnloadUnusedResources" is used
How to reproduce:
1. Open the “LoadSceneTest.zip“ project
2. Open File > Build Settings
3. Switch target platform to Windows StandalonePlayer
4. Enable “Development Build” and “Autoconnect Profiler”
5. “Build And Run” the project
6. In the Player, click “Set to 10 times”
7. Click the 'LoadScene empty2(Single)' button to move to empty2
8. Click the 'LoadScene empty(Single)' button to move to empty
9. Scroll down to the bottom of the Profiler to find the “Addressable Assets“ section
9. Observe the Autoconnected Profiler
Expected result: There is only one Scene currently loaded
Actual result: There are 20 Scenes currently loaded
Reproducible in: 1.23.1 (2022.3.58f1), 2.3.16 (6000.0.37f1, 6000.1.0b5, 6000.2.0a3)
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment