Hello Vision Pro Engineer, We have filed a bug report with ticket number FB21327973. A mini test app is included to demonstrate how the memory usage climbs significantly as we visit each space within a room. Thank you.

We found it interesting that the memory footprint increases as we first create a texture for a space, but if we visit the space again, the Persistent Bytes don't increase anymore, even though we are re-creating the texture for it. So we started wondering whether the textures were cached by the system, preventing it from being deallocated. Thank you, bvsdev

Hello Vision Pro Engineer, Yes, I will file a bug along with some code. For each room we use the same sphere entity. Within that room, as we navigate to different spaces, we "remove" the current space's texture by assigning it to nil after creating a new texture and material for the next space. Finally, as we leave a room (immersive space), we do a removeFromParent on the sphere, then set that sphere entity to nil as well. Thank you, we appreciate your insights.

Good morning @Vision Pro Engineer Would you be able to offer some insights into a similar problem my team is facing? The OS is shutting down our app due to high memory usage. In our app, each “room” is an immersive space with a skybox. Within the room we navigate through a variety of spaces, each with its own texture to be used in the skybox material. Each time we swap out the skybox material the memory usage grows significantly. VisionOS 26, Xcode 26.1.1

Hello giovanniR2U, Have you found a resolution/workaround to this problem in VisionOS 26 that you are able to share? We have come across the same problem with memory overload. Thank you, bvsdev