Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.2.3
Issue ID
AVPB-601
Regression
Yes
[visionOS] Memory usage increased between PolySpatial 1.1.4 and 1.2.3
Reproduction steps:
1. Create a new project
2. Build the project on “visionOS” platform (File > Build Settings > visionOS > Build)
3. Run the project on an Apple Vision Pro device
4. Observe the memory usage in XCode by selecting the Spay Bottle icon on the left window’s top bar
Expected result: The memory usage is at around 300MB (using simulator)
Actual result: The memory usage is at around 310MB (using simulator)
Reproducible with: 1.2.3 (2022.3.32f1)
Not reproducible with: 1.1.6 (2022.3.32f1)
Reproducible on: MR on visionOS 1.1 Simulator - built using M1 Max MacOS 14.5
Not reproducible on: No other environment tested
Notes:
- The exact amount how much memory isn’t as relevant, the issue is that there’s a noticeable increase in memory usage from 1.1.6 to 1.2.3
- The difference in memory usage between 1.1.6 and 1.2.3 increases with the project’s complexity. The users are seeing increases up to 300mb
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- SpeedTree importer fails to import .st files when path to the project includes a special character
- [VFX Graph] HSLS Redefinition error when input have the same name as attributes
- [VFX Graph] HLSL VFXFIXED_RAND isn't working
- Crash on Meta Quest 2 when using Vulkan
- Greyed out Icon for Tool Context is misaligned in the Tools Overlay in the URP 3D Sample Template
Resolution Note:
Expected increase as feature set increased