Search Issue Tracker
Won't Fix
Votes
24
Found in [Package]
1.1.0
Issue ID
PROFB-246
Regression
No
Part of memory usage is shown as "Unknown" in the Memory Profiler when taking a Snapshot of the Player
How to reproduce:
1. Open a new project
2. Make sure the Memory Profiler package is added (WIndow → Package Manager)
3. Open the attached “IN-81545_build“ folder and run the Player
4. In the Editor navigate to Window → Analysis → Memory Profiler
5. Make sure the Memory Profiler is connected to the Player
6. Take a Snapshot
7. Navigate to All Of Memory and expand Unity Subsystems
Expected result: The “Unknown“ section is not seen
Actual result: The “Unknown“ is seen
Reproducible with: 1.1.0-exp.1 (2022.3.12f1), 1.1.0 ( 2022.3.41f1, 6000.0.14f1)
Not reproducible with: 1.0.0 (2022.3.12f1)
Could not test with: 0.7.1-preview.1 (2021.3.42f1) (Memory Profiler was unable to take a Snapshot)
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Comments (2)
-
thiagolrosa
Jul 01, 2025 15:05
Really? 11 months and still not solved? Did you see how many developers have the same issue in the forums?
-
maxiboch
Jun 05, 2025 20:25
this would be a HUGE HUGE help in tracking down some memory issues that are plaguing the team working on Babysteps.
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:
Thank you for the bug report. We’ve taken a closer look at this and determined that the best way for us to deal with this is through a cross team initiative. To this end we are creating multiple internal tickets utilizing the reproduction projects from this and other bug reports for investigation and fix validation purposes.
Since this means voting on the bugs is no longer possible, nor is it possible to follow along on the status of the fix, we’ll move all of that into this Discussions thread (https://discussions.unity.com/t/unknown-memory-in-memory-profiler/920144/12). We’ll try our best to keep you updated on the status of this issue there.