Search Issue Tracker
Won't Fix
Won't Fix in 1.2.X
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Resolution Note:
Expected increase as feature set increased
Resolution Note (1.2.X):
Expected increase as feature set increased