Search Issue Tracker
Won't Fix
Votes
1
Found in
2022.2.8f1
Issue ID
UUM-31372
Regression
Yes
Error NullReferenceException: Object reference not set to an instance of an object when an UI Element contains a very large specific type of character set
Reproduction steps
1. Open the “UIElementBug” project
2. Press the “test” Button in the “TestWindow” Window
Expected result: Text is displayed in the Window
Actual result: No text is displayed in the Window and two identical errors (NullReferenceException: Object reference not set to an instance of an object) are displayed in the console
Reproducible with: 2022.1.0a11, 2022.1.24f1, 2022.2.8f1, 2023.1.0a21
Not reproducible with: 2020.3.44f1, 2021.3.18f1, 2022.1.0a10, 2023.2.0a2
Fixed in: 2023.1.0a22
Reproducible on: Intel MacOS 13.1
Notes:
- The issue does not occur when resizing the window a little and reopening it
- Pressing the button rapidly makes the issue disappears
- The issue disappears when resizing the window a lot
- Sub-menu items of “Test” all produce different windows with very similar results. The key difference is with the “test” sub-menu item producing the issue
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
The main issue has been fixed, and the underlying issue of performance impact is being addressed in future versions (2023.3 and forward).