I’ve been seeing some large discrepancies in how memory is managed or released on apps loaded on the device vs running through the simulator, where going to new scenes or unloading resources/addressables manually does clear memory as expected in the simulator but doesn’t seem to work on device but instead keeps a significant chunk of that memory, causing it to eventually build up over time and cause crashes. It also makes in next to impossible to create any form of “reset” button for the app as the second time it is played it is already starting at a major memory deficit on device, for example the reset button returns memory used to about 800mb on simulator but memory on device remains at over 2gb when the scene is reloaded. I can post screenshots of this or can try to make a repro case if necessary but first wanted to scope out whether anyone else has encountered this or if I’m missing something about how I should be managing memory in VisionOS.
Our project uses addressables to load and unload different major sections of the app as well so I’m wondering could it be related to these not being released correctly on device?
Any tips or pointers would be greatly appreciated!