Search Issue Tracker
Third Party Issue
Votes
1
Found in
2019.3
2019.3.7f1
2020.2
Issue ID
1231634
Regression
No
[Linux][Vulkan] Crash on _nv043glcore when logging back into system after suspending it
Reproduction steps:
1. Open a new or an existing project
2. Change the Graphics API from OpenGL Core to Vulkan
3. Suspend the system (either by running the command 'systemctl suspend' or through the system settings)
4. Log back into the system
Reproducible with: 2019.3.9f1, 2020.1.0b5, 2020.3.4f1, 2021.1.5f1 2021.2.0a15
Could not test with: 2017.4.39f1 (due to this version not yet properly supporting Vulkan), 2018.4.20f1 (reason described below)
First 5 lines of the stack trace:
#0 0x007f198afb0613 in _nv043glcore
#1 0x007f198afc6130 in _nv043glcore
#2 0x0055f2492a8017 in vk::Image::CreateImageViews(VkDevice_T, VkComponentMapping, VkFormat, bool, VkFormat)
#3 0x0055f2492f53d1 in vk::ImageManager::CreateImage(TextureDimension, int, VkExtent3D const&, DepthBufferFormat, int, unsigned int, VkSampleCountFlagBits, vk::ImageMemory)
#4 0x0055f2492af270 in vk::Texture::Create(vk::CommandBuffer, TextureID, TextureDimension, int, VkExtent3D const&, DepthBufferFormat, ShadowSamplingMode, int, VkSampleCountFlagBits, vk::ImageMemory)
Notes:
- The Issue was reproduced with Ubuntu 18.04 and reported from Kali Linux
- Suspending the system while Unity 2018.4.20f1 is open results in the display not working when turned back on, a reboot is required which then prevents the crash from happening
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (2020.2.X):
NVidia mentioned that it is by design and we will need to handle device lost on our end so that we can recover from the error. We are tracking it as a work-item and will be available in a future release.