Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.17f1
2022.2.4f1
2023.1.0a26
Issue ID
UUM-24829
Regression
No
[Profiler] Memory module reports the allocated memory more than the "Total" value
How to reproduce:
1. Open a new Unity project
2. Run the user’s attached “MemoryTest” apk file
3. Observe the values of “Memory” module in the Profiler
4. Select memory for allocation using the scroller right to “DestroyAll” button
5. Click the “LoadAndInstance” button to allocate as much memory as possible for the device
6. Observe the reported percentage of used memory in the module
Expected result: The report for “Total” and “Graphics & Graphics Driver” allocated memory is correct
Actual result: “Graphics & Graphics Driver” memory allocation is reported higher than “Total” one
Reproducible with: 2021.3.17f1, 2022.2.4f1, 2023.1.0a26
Couldn’t test with: 2020.3.44f1 (error on connection)
Reproduced on: macOS 13.1 (Intel)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
We will close this bug due to it only seeming to happen on this particular project. We'd recommend the customer try it again using version 2023 and higher, with the Memory Profiler installed. If they still get this error, please let us know.