Search Issue Tracker
Not Reproducible
Votes
2
Found in
2018.3.0a4
2019.2.0a1
2019.2.1f1
2019.3.0a1
2020.1.0a1
Issue ID
1178153
Regression
Yes
[Vulkan] Semaphore.WaitForSignal goes up to 500ms when resizing any Editor window
Steps to repro:
1. Create a new project
2. Set Graphics API to "Vulkan"
3. Try to resize any window
Expected result: Editor does not lag
Actual result: Editor lags, Semaphore.WaitForSignal goes up to 500ms (seen in profiler)
Reproduced in: 2018.3.0a4, 2018.4.7f1, 2019.2.3f2, 2019.3.0b1, 2020.1.0a1, 2020.1.0a2
Not reproduced in: 2018.3.0a3 and lower streams
Note: Only reproducible with Nvidia GPU's, confirmed issue with GeForce 1070 using drivers:
Nvidia Studio Driver 431.70 (dch)
Nvidia Studio Driver 430.86 (dch)
No issue found with GeForce 1070 using drivers:
Nvidia Game Ready Driver 399.24 (dch)
Nvidia Game Ready Driver 436.15 (dch)
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
Reproducible with Nvidia driver 431.36, but not reproducible in 441.66. Please try to update your graphics card driver to latest version.