Search Issue Tracker
Fixed in 1.7.0
Votes
1
Found in
1.17.0-pre.2
Issue ID
UUM-135657
Regression
No
XR Composition Layers allocate 160B every frame when in Play mode
How to reproduce:
1. Create a new project using the VR template
2. Enter Play mode
3. Go to Window > Analysis > Profiler
4. Observe the method being executed in the Profiler window
Actual result: 160B allocations visible every frame
Expected result: Allocation is not called every frame
Reproducible with: 1.0.0 (6000.0.68f1), 2.3.0 (6000.0.68f1, 6000.3.10f1, 6000.4.0b9, 6000.5.0a7)
Reproducible on: Windows 11 pro
Not reproducible on: No other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprite Atlas textures from all included build scenes persist in Editor memory when building the Player
- Disabling all columns in Light Explorer throws “ArgumentException” error in the Console window
- Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
Add comment