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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.