Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
1
Found in
2020.3.38f1
Issue ID
UUM-1583
Regression
Yes
Linux build using Vulkan becomes unresponsive when changing window resolution
How to reproduce:
1. Open the user's attached project
2. Open scene Scenes/SampleScene
3. Go to File -> Build Settings and select "Add Open Scenes"
4. Build the project for Linux
5. Run the build via the Terminal with additional parameters "-force-vulkan"
Expected result: the build continues to run while rapidly changing resolution
Actual result: the resolution changes and the build freezes / is not responding
Reproducible with: 2020.3.28f1, 2020.3.33f1
Not reproducible with: 2019.4.38f1, 2020.3.27f1, 2021.3.1f1, 2022.1.0f1
Could not test with: 2022.2.0a11 ('SysrootPackage' does not implement inherited abstract member 'Sysroot.GetToolchainPath()')
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
- [Linux] Navigating Prefab Components in Overrides window shows rendering artifacts in the Editor
- Prefab Overrides window cuts-off Component labels across multiple Components
- Opening Memory Settings documentation from Project Settings window opens missing page
- Animated GameObjects ignore Shader keywords when running on VisionOS Player with Polyspatial
- Quickly clicking "Open query in Search Window" in the Hierarchy twice opens the two Search tabs at the same time
Resolution Note:
Tested on Ubuntu 22.04.1 LTS with the user attached project with "-force-vulkan" command line switch and could not reproduce this issue.
- NVIDIA driver version: 515.65.01
Resolution Note (2020.3.X):
Tested on Ubuntu 22.04.1 LTS with the user attached project with "-force-vulkan" command line switch and could not reproduce this issue.
- NVIDIA driver version: 515.65.01