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
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
- InvalidOperationException when using Game Camera Preview in Scene window with a custom RenderGraph pass
- Changing "PreWarm" parameters on VFX Graph leads to significant performance drops and freeze due to rapid changes in "Total Time"
- Player display resolution changes to the native resolution of the monitor when Player becomes unresponsive
- [Quest] Game View is no longer rendered in the HMD if it's hidden in the Editor when using Meta Link
Add comment