Search Issue Tracker
Fixed
Fixed in 2022.3.63f1, 6000.0.50f1, 6000.1.4f1, 6000.2.0b2, 7000.0.0a28
Votes
0
Found in
2022.3.0f1
6000.0.0f1
6000.1.0a6
6000.2.0a1
7000.0.0a1
Issue ID
UUM-90434
Regression
No
Crash on EditorDisplayDialogProc when opening Dialog box containing buttons with unusually long labels
Reproduction steps:
1. Open the attached “IN-89307.zip” project
2. In the menu, click on Tools > Explode
3. Observe the crash
Reproducible in: 2021.3.46f1, 2022.3.53f1, 6000.0.29f1, 6000.1.0a6
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
First few lines of stacktrace:
{noformat}0x00007ff60866df9f (Unity) EditorDisplayDialogProc
0x00007fff560031cf (USER32) ScreenToClient
0x00007fff56002912 (USER32) ScreenToClient
0x00007fff56002826 (USER32) ScreenToClient
0x00007fff55ffef5c (USER32) CallWindowProcW{noformat}
Note: If “Explode” is not clickable, restart the Editor and try again.
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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
Resolution Note (fix version 7000.0.0a28):
Verified the fix has landed in 7000.0.0a23 using Windows 11
Resolution Note (fix version 6000.2.0b2):
The string management has been fixed to prevent a crash when using long label names in the dialog method.
Resolution Note (fix version 2022.3.63f1):
Verified the fix has landed to 2022.3.64f1