Search Issue Tracker
Won't Fix
Won't Fix in 1.1.X
Votes
0
Found in [Package]
1.1.0
1.1.1
Issue ID
PROFB-253
Regression
No
Part of memory usage is shown as "Unknown" in the Memory Profiler when taking a Snapshot of the Player
How to reprouduce:
1. Open a new project
2. Make sure the Memory Profiler package is added (WIndow → Package Manager)
3. Open the attached “IN-84207_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 ( 2022.3.46f1, 6000.0.14f1), 1.1.1 ( 6000.0.19f1)
Could not test with: 0.7.1-preview.1 (2021.3.42f1) (Memory Profiler was unable to take a Snapshot)
Reproducible on: Windows 11 Pro, Nintendo Switch
Not reproducible on: No other environment tested
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
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.
Resolution Note (1.1.X):
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.