Isaac Sim 2023.1.0 Fails Due to Vulkan Issue on Ubuntu 20.04

[gmetts]

Hello,

I run into the following issue when trying to launch 2023.1.0 on Ubuntu 20.04.

2023-11-01 21:36:51 [754ms] [Info] [omni.kit.renderer.plugin] Attaching default app window “Isaac Sim App Selector 105.1+release.129498.98d86eae.tc”
2023-11-01 21:36:51 [984ms] [Error] [carb.graphics-vulkan.plugin] VkResult: ERROR_INITIALIZATION_FAILED
2023-11-01 21:36:51 [984ms] [Error] [carb.graphics-vulkan.plugin] vkCreateSwapchainKHR failed.
2023-11-01 21:36:51 [984ms] [Error] [carb.graphics-vulkan.plugin] Failed to create a swapchain.

Note, that this happens when trying to run the AppSelector, or running Isaac 2023.1.0 direct from .sh script.

I am running precisely the 525.85.05 Nvidia driver recommended by the install guide.

|---------------------------------------------------------------------------------------------|
| Driver Version: 525.85.05 | Graphics API: Vulkan
|=============================================================================================|
| GPU | Name | Active | LDA | GPU Memory | Vendor-ID | LUID |
| | | | | | Device-ID | UUID |
| | | | | | Bus-ID | |
|---------------------------------------------------------------------------------------------|
| 0 | NVIDIA GeForce RTX 3080 | Yes: 0 | | 10486 MB | 10de | 0 |
| | | | | | 2216 | 1e8bc2a3… |
| | | | | | b | |
|=============================================================================================|
| OS: 20.04.6 LTS (Focal Fossa) ubuntu, Version: 20.04.6, Kernel: 5.15.0-88-generic
| XServer Vendor: The X.Org Foundation, XServer Version: 12013000 (1.20.13.0)
| Processor: AMD Ryzen 7 5800 8-Core Processor | Cores: 8 | Logical: 16
|---------------------------------------------------------------------------------------------|
| Total Memory (MB): 48092 | Free Memory: 45646
| Total Page/Swap (MB): 2047 | Free Page/Swap: 2047
|---------------------------------------------------------------------------------------------|

My Vulkan Instance Version is 1.2.131 and was clean installed from the .run file for 525.85.05. From other forum posts, I’ve tried deleting the folders in /etc and /usr to make sure there are no leftover files.

Attached are the full outputs from vulkaninfo and the log from an attempt to open 2023.1.0.

kit_20231101_173650.log (243.4 KB)
vulkaninfo.txt (51.8 KB)

It is worth mentioning that 2022.2.1 opens fine on this machine with this exact configuration. It is also worth mentioning is that 2023.1.0 will run in native headless mode with little issue.

I am attempting to roll forward to 2023.1.0 in order to see if it performs better when clearing GPU memory. On Ubuntu (20.04) the program does not properly clear the allocated GPU memory, causing issues when working in it over time, or trying to create many instances for training. These issues are not present when running on Windows 11. I have no issues installing either 2023.1.0 or 2022.2.1 or issues with GPU memory when closing and opening new instances.

This may be worthy of its own post in itself.

Edit 1: I accidentally made a mistake creating my vulkaninfo.txt file and corrected it 11/02

[Sheikh_Dawood]

Hi. Thanks for the logs. I found this:

2023-11-01 21:36:51 [984ms] [Error] [carb.graphics-vulkan.plugin] VkResult: ERROR_INITIALIZATION_FAILED
2023-11-01 21:36:51 [984ms] [Error] [carb.graphics-vulkan.plugin] vkCreateSwapchainKHR failed.
2023-11-01 21:36:51 [984ms] [Error] [carb.graphics-vulkan.plugin] Failed to create a swapchain.
2023-11-01 21:36:51 [984ms] [Error] [omni.kit.renderer.plugin] createSwapchain failed. Width: 65516, height: 530, Format: 9
2023-11-01 21:36:51 [984ms] [Error] [omni.kit.renderer.plugin] Failed to initialize graphics environment.

Can you try run Isaac Sim directly in a terminal with --reset-user to reset the config. If this does not help try uninstall the drivers or any CUDA or Vulkan sdk/tools, reboot then reinstall the latest 525.x drivers using the .run installer.

[sujitvasanth]

Hi Im running ubuntu 20.04 and version 2023.1.0 without any issues

here is my console details

| Driver Version: 525.125.06    | Graphics API: Vulkan
|=============================================================================================|
| GPU | Name                             | Active | LDA | GPU Memory | Vendor-ID | LUID       |
|     |                                  |        |     |            | Device-ID | UUID       |
|     |                                  |        |     |            | Bus-ID    |            |
|---------------------------------------------------------------------------------------------|
| 0   | NVIDIA GeForce RTX 3090          | Yes: 0 |     | 24822   MB | 10de      | 0          |
|     |                                  |        |     |            | 2204      | ff1d819d.. |
|     |                                  |        |     |            | 9         |            |
|=============================================================================================|
| OS: 20.04.5 LTS (Focal Fossa) ubuntu, Version: 20.04.5, Kernel: 5.15.0-56-generic
| XServer Vendor: The X.Org Foundation, XServer Version: 12013000 (1.20.13.0)
| Processor: AMD Ryzen 7 5800X 8-Core Processor | Cores: 8 | Logical: 16
|---------------------------------------------------------------------------------------------|
| Total Memory (MB): 64212 | Free Memory: 53221
| Total Page/Swap (MB): 2048 | Free Page/Swap: 2048
|---------------------------------------------------------------------------------------------|

hope that might be of some help
sincerely
Sujit

[gmetts]

I finally figured out what was causing this issue.

In certain display configurations, Nvidia’s usage of the Vulkan renderer will crash.

For example, the following will run successfully.

However this will fail.

Any 2 monitor configuration I’ve tried seems to work in any configuration. But I have not taken the time to test extensively.

The vulkan test command vkcube seems to work regardless, so it’s unlikely a general vulkan issue, but more likely an implementation edge-case issue in the application.

I’d recommend that anyone seeing a similar error, attempt to run a single monitor setup to eliminate this fringe issue as a possibility.