Search Issue Tracker
Won't Fix
Won't Fix in 1.0.X
Votes
0
Found in [Package]
0.7.1-preview.1
1.0.0
Issue ID
PROFB-88
Regression
No
Memory Profiler can not display the values correctly when the value is made from more than one line
Reproduction steps:
1. Open the attached project “MemoryProfilerBug“
2. Open the Memory Profiler (Window>Analysis>Memory Profiler)
3. In the Open Snapshots pane select the snapshot “Snap1”
4. Open the tab “All Of Memory”
5. Expand the list items (Scripting Memory>Managed Objects>UnityEngine.Font)
6. Select the list item “<No Name>”
7. Look at the “Managed Fields” table
Expected results: Values are displayed clearly
Actual results: Values with more than one line are not displayed properly
Reproducible with: 0.7.1-preview.1 (2020.3.44f1, 2021.3.17f1, 2022.1.24f1), 1.0.0 (2022.2.3f1, 2023.1.0b1, 2023.2.0a3)
Reproducible on: Windows 11
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 reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (1.0.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.