Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X
Votes
0
Found in
2018.3.12f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1162014
Regression
No
XRNodeState TryGet methods allocate memory when controllers are not being tracked
How to reproduce:
1. Create a new Unity project
2. Use XRNodeState's "TryGet<T>" function when the node is not being tracked
3. Inspect the allocated memory in the Profiler
Expected results: Allocated memory remains the same
Actual results: Allocated memory increases
Reproducible with: 2018.4.3f1, 2019.1.0a6, 2019.2.0a3, 2019.3.0a1
Not reproducible with: 2019.1.0a7, 2019.1.0b3, 2019.2.0a4, 2019.3.0a2
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Up, Down and other Buttons in a Style Sheet's Inspector unselect items when they are clicked while they are disabled
- Virtual Player remains active and still launches when removed from Additional Editor Instances from a custom Play Mode Scenario
- UI Toolkit Editor Window Creator becomes not interactable and greyed out when a long name is entered
- [Web][iOS] Web Player keeps restarting on launch when Native C/C++ Multithreading is enabled
- "Add Scene to Scenes in Build" pop-up reappears after Scene has already been added and another Multiplayer Editor Instance is loaded
Resolution Note (fix version 2019.3):
Fixed in 2018.4.4f1, 2019.1.0a7, 2019.2.0a4, 2019.3.0a2