Search Issue Tracker
Fixed in 3.2.17
Votes
0
Found in [Package]
3.2.15
Issue ID
1268703
Regression
No
[XR SDK] Player.log is spammed with Internal allocation messages when initializing XR manually
Reproduction steps:
1. Make sure HMD is connected and working
2. Open the attached project ("New Unity Project.zip")
3. Build and Run the project (While in-game don't move the Headset)
4. Open Build Player.log file
Expected result: Console isn't spammed with "Internal: ..." messages
Actual result: Console is spammed with "Internal: deleting an allocation that is older than its permitted lifetime of 4 frames" messages
Reproducible with: XR SDK 3.2.15 (2019.4.12f1, 2020.1.8f1, 2020.2.0b6)
Could not test with: 2018.4.28f1 (XR SDK not available)
Tested with:
- Oculus Rift
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Add comment