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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment