Search Issue Tracker
Fixed
Fixed in 2021.3.17f1, 2022.2.4f1
Votes
0
Found in
2020.3.41f1
2021.3.13f1
2022.1.23f1
2022.2.0b15
2023.1.0a2
Issue ID
UUM-21096
Regression
No
The Unity Editor becomes unresponsive when a modal window loses focus and an aux window exists
How to reproduce:
1. Open the attached user project “ModalWindowFromAuxWindowEditorFreeze.zip“
2. Open the “Aux Window“ window (Bug Report>Open Aux Window)
3. Press the “Open Modal Window“ button
4. Un-focus the Unity Editor window
5. Focus on the Unity Editor window
Expected result: The “Modal Window“ window is shown, it is possible to close the window and continue using the Editor
Actual result: The “Modal Window“ window isn’t shown, the Editor is unresponsive
Reproducible with: 2020.3.41f1, 2021.3.13f1, 2022.1.23f1, 2022.2.0b15, 2023.1.0a2
Not reproducible with: 2023.1.0a3, 2023.1.0a20
Reproduced on: Windows 10 (19044.2251)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment