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
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
Resolution Note (fix version 2019.3):
Fixed in 2018.4.4f1, 2019.1.0a7, 2019.2.0a4, 2019.3.0a2