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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Add comment