Search Issue Tracker
Fixed in 2017.2.X
Votes
2
Found in
5.6.0f3
Issue ID
898495
Regression
Yes
[HoloLens] Memory usage in release builds is 2x larger compared with debug/master configuration builds
Steps to reproduce:
1. Open attached project
2. Build WSA Universal 10 solution
3. Open VS solution
4. Deploy on HoloLens using debug/master configuration
5. Take a note about memory usage
6. Deploy on HoloLens using release configuration
7. Compare memory usage between debug/master and release configuration builds
Expected result: memory usage shouldn't differ much between diffent configuration builds
Actual result: builds with release configuration use 2x more memory on HoloLens device
Reproducible with: 5.5.2f1, 5.5.3p1, 5.6.0b9, 5.6.0f3, 2017.1.0b1
Not reproducible with: 5.5.0f3
Not reproducible when deployed on local machine
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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
holo-krzysztof
Jun 20, 2017 12:24
Apparently this has been fixed in version 5.5.4.
I haven't found any mention of this in the release notes, but as of my testing with an empty scene project the regression seems to be gone.