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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment