Search Issue Tracker
Active
Under Consideration for 1.1.X
Votes
16
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Add comment