Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.1.X
Votes
0
Found in
2019.2.0a6
Issue ID
1138251
Regression
No
[UWP][WindowsMR] - 2018.3 - Memory leak - 1 MB/minute in a UWP VR project due to Spatial Mapping
On 2018.3 in a blank project, I exported a UWPPlayer that supports WMR. I'm observing a small leak that aligns with Chris' description. Looks like legacy HoloLensWorldManager code is holding on to a COM reference indefinitely each time we call TryGetSpatialStage which is frequently.
Repro Steps:
1.) Download the repro project
2.) Open the project
3.) Build for HoloLens
4.) Deploy to HoloLens
5.) Attach the profiler
Actual
Looks like legacy HoloLensWorldManager code is holding on to a COM reference indefinitely each time we call TryGetSpatialStage which is frequently.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UnityLinker causes crash when outputting snapshot data for very large projects
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
Add comment