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 ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment