Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.21f1
2022.2.12f1
2023.1.0b9
2023.2.0a7
2023.3.0a3
Issue ID
UUM-30910
Regression
No
Crash on objc_release when TextField in custom Window is selected on MacOS
Reproduction steps:
1. Open the attached “CrashRepro” project
2. Go to Scenarios > Scenarios then press on "ScenarioTest" - this will open a Window with TextFields
3. Press on any of the TexFields
Expected result: TextField is selected and you can input values
Actual result: Editor freezes or crashes
Reproducible with: 2021.3.21f1, 2022.2.12f1, 2023.1.0b9, 2023.2.0a7
Could not test with: 2020.3.46f1 (“Scenarios” Menu item is not visible)
Reproducible on: macOS Ventura 13.2.1 (M1 Max), macOS Ventura 13.2.1 (Intel)
Not reproducible on: Windows 10
Stacktrace:
#0 0x00000199b04278 in objc_release
#1 0x4a36800199b08870 in objc_autoreleasePoolPop
#2 0x311c000199f11c24 in _CFAutoreleasePoolPop
#3 0xc40c00019ae30464 in -[NSAutoreleasePool drain]
#4 0x261880019d1c8ed0 in -[NSApplication run]
#5 0xd95280019d1a0250 in NSApplicationMain
#6 0x83630001032190d8 in EditorMain(int, char const**)
#7 0x00000103219410 in main
#8 0x00000199b47e50 in start
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:
Could not reproduce on 2023.3.0b11
Likely fixed by another bug