LoadSceneAsync not unloading all assets

Hello I am having issues with assets persisting over scenes while they should unload and was wondering if somebody here could help me out.
I am currently on Unity 2019.3.11f1 and Addressables 1.12.0.

If I continuosly switch between our main menu and ingame scenes we get an increase in live objects and we seem to not destroy the threads that were used to load our assetbundles. On platforms with low thread counts this makes the application crash after 2-3 times.

Most of our assets are addressables and bundled in assetbundles but we are not loading those ourselves, we only load our scenes through addressables and they will then load the assets that are needed from the other bundles.

If you look at the following screenshots (both are taken in the main menu, second is after we loaded into a gamescene and returned back to the main menu with LoadMode.Single from LoadSceneAsync) you can clearly see that almost everything increased in number and size while to my knowledge it should almost be the exact same.




So then I want to the memory profiler to can a more indepth view and I noticed that we have quite some objects that have a refcount of 0 that are not unloaded, I only show a few here but there are a ton.

I know assetbundles can partially load but not partially unload except if we call Resources.UnloadUnusedAssets, which I tried as well but it does not seem to have an impact at all.

And if I look at the crashdump I see threads that are not being used anymore but that aren't destroyed which I speculate is because we failed midway while unloading assetbundles.


I have been trying to reproduce this issue in a small sampleproject to no succes as of yet.

TLDR: Our threads do not seem to be released because LoadSceneAsnc cannot correctly release all its related assets. Could someone give me a bit more insight on this?

 

HI @TreyK-47

It turns out it was not specifically linked to scene loading.

Case: 1268994