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
- Errors "InvalidOperationException: Trying to use a texture (_InternalGradingLut)..." and “Render Graph Execution error” shown and Scene turns black when 16 or more Render Objects are used
- GameObjects in the Game View are rendered differently than in the Scene View when the Rendering Path is set to "Deferred" and Screen Space Shadows Renderer Feature is added
- Errors “InvalidOperationException: Trying to use a texture (_CameraDepthTexture)...” and “Render Graph Execution error” shown when selecting GameObjects with Mesh Renderer from the Hierarchy
- macOS stutters in a minimal project
- [Usability] HDRP Wizard calls for VR fixes when opening the HDRP Wizard a second time after they have already been applied and the Wizard has finished checking
Add comment