Search Issue Tracker
Duplicate
Duplicate in 1.0.X
Votes
0
Found in [Package]
1.0.0-pre.3
Issue ID
PROFB-26
Regression
No
Non-Latin characters are displayed incorrectly in Memory Profiler
Reproduction steps:
1. Open the “TestMemoryProfiler” project
2. Open Memory Profiler by Windows -> Analysis -> Memory Profiler
3. On the left side of the Memory Profiler window select the available snapshot
4. In the Memory Profiler window go to the Summary tab
5. Click on the "Texture2D" block
6. On the bottom of the Memory Profiler window locate an asset that has "1234" in its name
Expected result: Asset has Chinese characters in its name
Actual result: Asset name is not displayed correctly
Reproducible with: 0.7.1-preview.2 (2020.3.37f1, 2021.3.6f1, 2022.1.10f1), 1.0.0-pre.3 (2022.2.0b2, 2023.1.0a4)
Reproduced on: Windows 10
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Duplicate of https://jira.unity3d.com/browse/PROF-2217
Fixed in Memory Profiler 1.0.0 Release
Duplicate of another internal issue: PROFB-26: Non-Latin characters are displayed incorrectly in Memory Profiler
Resolution Note (1.0.X):
Duplicate of https://jira.unity3d.com/browse/PROF-2217
Fixed in Memory Profiler 1.0.0 Release
Duplicate of another internal issue: PROFB-26: Non-Latin characters are displayed incorrectly in Memory Profiler