Search Issue Tracker
Fixed in 2022.3.59f1
Fixed in 2022.3.X, 6000.0.X, 6000.0.40f1, 6000.1.0b5, 6000.2.X, future release
Votes
0
Found in
2022.3.44f1
6000.0.17f1
Issue ID
UUM-79065
Regression
Yes
Crash on DispatchMessageW when using FolderBrowserDialog
Reproduction steps:
1. Open the attached project "CrashRepro"
2. Enter the Play mode
4. Focus a different window
5. Close the FolderBrowserDialog
6. Exit Play mode
7. Repeat from 2-6 until crash
Expected result: Editor exits Play mode
Actual result: Editor crashes
Reproducible with: 2022.2.0a1, 2022.3.44f1, 6000.0.17f1
Not reproducible with: 2021.3.42f1, 2022.1.0b1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
Reproduces very inconsistently
Sometimes crashes silently
Throws win32 error 487 on older editor versions (~below 2022.2.0b1)
First few lines of stack trace:
{noformat}0x00007FFE48A982E1 (USER32) DispatchMessageW
0x00007FFE48A97F9C (USER32) DispatchMessageW
0x00007FFE48AA30CD (USER32) GetClassLongW
0x00007FFE49B93FE4 (ntdll) KiUserCallbackDispatcher
0x00007FFE470E1534 (win32u) NtUserGetMessage
0x00007FFE48AA53FA (USER32) GetMessageW{noformat}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment