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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
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.