Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.2.3f1
2023.1.0a26
2023.2.0a1
Issue ID
UUM-22929
Regression
No
Warning Spam: The character with Unicode value □ was not found in the [] font asset or any potential fallbacks. It was replaced
How to reproduce:
1. Open the attached project “IN-28531.zip“
2. Open the Memory Profiler (Window > Analysis > Memory Profiler)
4. Open the “All Of Memory” tab
5. Expand the “Scripting Memory > Managed Objects > System.String”
6. Select the biggest string (1.6 KB, should by default be at the top.)
7. Observe the Console Output.
Expected result: No warnings are present in the Console window
Actual result: Lots of warnings are present in the Console window
Reproducible with: 1.0.0 (2022.2.0a16, 2022.2.3f1, 2023.1.0a26)
Couldn’t test with: 0.7.1-preview.1 and lower - Memory Breakdowns option is unavailable
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
There are no fixes planned for this Bug