Search Issue Tracker
Won't Fix
Votes
0
Found in
5.1.0b5
Issue ID
694915
Regression
Yes
Differences between Memory Usage Shown in Profiler and in Windows Task Manager
Reproduction steps:
1. Open attached project "GetPixelsLargeTex"
2. Open scene "ImportBigFile"
3. Hit play, let the scene run in the editor for a few seconds
4. Quit before too much memory is hogged
Notes:
1. Notice that Commit size (in Windos Task Manager) doesn't match neither Reserved Total nor Total System Memory Usage (in the Profiler)
2. See attached image for Task Manager and Profiler Values on my pc (MemoryScreen.png)
3. Not 100% sure that this is a regression, but in 5.0.0b1 Total System Memory Usage and Commit size did match
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Look Dev constantly regenerates the default Volume Profile when set to "None" instead of using the default one
- Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
- URP Scene Templates are not editable when first opened from the New Scene dialog
- Look Dev window flickers when resizing the window after docking it
- UI breaks when Multiplayer Center window section divider is moved too far
Add comment