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
- Video preview in the Inspector freezes shortly after the first play and does not recover until paused and replayed
- MSB3277 conflicts between different versions of "System.Numerics.Vectors" when using DotNet 11.0
- "Cannot create Settings Providers for: CreateAllChildSettingsProviders" error is thrown in the Console after fixing PolySpatial visionOS package validation error after installing XR Interaction Toolkit VisionOS Sample
- "Unable to find style 'VideoClipImporterLabel' in skin 'GameSkin' " warning thrown when converting the Video Clip Inspector to a floating window in Play mode
- Unclear "Failed to start primary listening socket" error when launching the Multiplayer Play Mode second player and many Unity instances are running
Add comment