Search Issue Tracker
Fixed
Fixed in 1.0.0
Votes
0
Found in [Package]
0.7.1-preview.1
1.0.0-pre.3
Issue ID
PROFB-89
Regression
No
Incorrect Texture2D name encoding when a snapshot is taken in memory profiler
Reproduction steps:
1. Open the attached project “ProfilerProject”
2. Open the “Assets/Scenes/SampleScene.unity” scene
3. In the Project Window, Observe the name of the Texture2D asset (nonascii贴图で)
4. Enter Play Mode
5. Open the “Window>Analysis>Memory Profiler” Window, click “Capture New Snapshot”
6. Select the new Snapshot created and switch to Tree Map View
7. Click Texture 2D
8. Observe the name of the Texture
Expected result: The Texture2D asset name is displayed as 'nonascii贴图で'
Actual result: Texture2D name is displayed as 'nonasciiè´´å¾ã§'
Reproducible with: 0.7.1-preview.1 (2020.3.45f1, 2021.3.18f1), 1.0.0-pre.3 (2022.2.0b9)
Not Reproducible with: 1.0.0 (2023.1.0b6, 2023.2.0a4)
Fixed in: 1.0.0 (2022.2.6f1)
Reproducible on: Intel macOS 13.0.1
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
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
- Graphics Compositor breaks Unity rendering when the "Output Camera" is changed to a scene Camera and one Camera SubLayer is active
- The Editor freezes on RenderGraphViewer.Repaint when entering too many characters in search fields without character limits
- Adding a new SubLayer in Graphics Compositor renders BaseLayer darker and makes it flicker
Resolution Note (fix version 1.0.0):
Non Ascii characters are now shown correctly