Track Loaded / Unloaded Bundles

How can we check which bundles have been loaded into memory and when they are unloaded? I am testing loading a prefab through addressables, and then testing unloading it through addressables. How can I verify that a bundle has been unloaded and the memory for that is free'd up?

On another note when using the event viewer I am not getting any ref counts within the viewer for when loading and unloading, which is hard to track the bundles correctly.

It would be great to get a guide on how to do this properly. We are concerned of a memory leak right now because bundles are not being unloaded properly.

Adam

 

Any help here is appreciated.

 

I also would like to know about this. Currently I have been using the memory profiler but it seems a bit clunky to have to take a snapshot and then analyze that when the addressables system should already have knowledge about whats loaded and unloaded

 

@cg-adam the event viewer tracks memory usage with the loaded / unloaded bundles. What other functionality are you looking for?

 

Well, for one it does not seem to work (as per my original post). In all modes I have tried in the editor it is very hard to tell what is loaded and unloaded (plus there are multiple threads on here relating to handles not being disposed properly).

Second, I really want something at runtime. They clearly have a system which checks to see if a bundle can be unloaded (as this is what they use to unload the bundles) but we do not have access to it.

 

Our issue is that we have a project with multiple games inside it, these games are stored in bundles which the addressables system loads when required. However when going back into the Lobby and launching a new game, the previous bundles are not unloaded, eventually causing memory issues and crashes. We are struggling at times to find out WHY a bundle is not being unloaded, what it keeping it loaded / in memory, and how to force it to unload. It would be great if there was a tool to track an individual bundle, its assets, and what is causing it to be kept alive in memory.

 

+1