Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
Issue ID
1235986
Regression
Yes
Closing a modal window hits a DebugAssert and crashes unity.
I have stumbled on this in the Shortcut Manager conflict window, but Looking at the code, it probably happens to any modal window that calls into EditorWindow.Close.
Steps to reproduce:
- Open Shortcut Manager and create a conflict
- For example, bind "Main Menu/Assets/Clear Shader Cache" and "Main Menu/Assets/Create/Animation" both to Ctrl+J
- Close the Shortcut Manager window
- Press Ctrl+J
- A Short Conflict modal window opens up
- Click cancel
- Crash!
The crash happens in the ContainerWindow destructor.
I'm pretty sure this used to work on 2018.x, because this flow was tested during the development of the Shortcut manager
Reproducible with: 2020.2.0a8.917
Not Reproducible with: 2020.1.0b3.3385
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