2.20 Crash of the editor launch [Intel Arc; Linux]

[Blaysht]

Good afternoon, when trying to launch the newly created project editor on version Community 2.20, an emergency stop occurs with the message "Received signal SIGSEGV, invalid memory reference". At the same time, on versions of Community 2.11.0.2 and Community 2.19.0.1, the editor is opened normally and the work in them is not accompanied by any errors.

Environment:

• Distribution: ALT Regular (see os-release);
• Kernel: Linux 6.16.5-6.16-alt1 x86_64;
• Driver: Mesa 25.2.2 [Xe DRM] (see glxinfo.txt and vulkaninfo.txt);
• GPU: Intel Arc A770 8GB

Logs:

• STDOUT (see STDOUT.txt);
• Browser (see browser_0.log);
• Editor (see editor_log.txt);

 

EDIT:

Tested on i915 DRM and didn't launch any of the editors at all.

• Community 2.20 and Community 2.19.0.1: [ERROR] "Unigine fatal error: VkExt::init(): Failed to initialize GPU Adapter - GPU Adapter doesn't have additional queue family with transfer"
• Community 2.11.0.2: [ERROR] "Received signal SIGSEGV, invalid memory reference"

Edited September 9, 2025 by Blaysht

[silent]

Blaysht

The main issue here is the lack of support of required feature for async transfer in Intel Vulkan GPU driver.

Engine is using multiple threads to submit data from CPU to GPU on Vulkan and your driver is not letting us to do so. If you will try to find VkQueueFamilyProperties in the vulkaninfo.txt you can see that queueCount is always = 1. However, the minimal number that will allow engine to work is 2.

Once this feature is supported by the Intel GPU driver, the engine will start working automatically.

Older versions (such as 2.11) may still function because they also have OpenGL support under Linux.

Crashes on i915 may also indicate driver-related issues. Please note that UNIGINE 2.11 still requires at least OpenGL 4.5 Core Profile support.

Thanks!

[Blaysht]

Thanks for the clarification!

Strangely, it seems that I recently looked at Windows in vulkan with about the same number of queues. Unfortunately, the vulkan.gpuinfo.org It's not working right now for some reason, so I can't confirm the information.

Most likely, I'll pump Windows tomorrow to check the performance of the engine there.

Edited September 9, 2025 by Blaysht

[silent]

On Windows you can always use DX12, it should work for the most cases.