Vulkan Device Out of Memory after 5.1.1 project migration

I have a simple UI project developed on Linux in version 5.0.3. The shipping binary works perfectly fine when deployed to targets.

I updated my unreal engine version to 5.1.1, opened the same project and rebuilt the shipping binary. This shipping binary runs fine on my dev machine, but when deployed to targets, the following segfault occurs:

5.1.1-0+++UE5+Release-5.1 1008 0
Disabling core dumps.
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0

Failed to find symbol file, expected location:
"/home/azul/UpdatedFE/AzulFrontend/Binaries/Linux/AzulFrontend-Linux-Shipping.sym"
LowLevelFatalError [File:./Runtime/VulkanRHI/Private/VulkanUtil.cpp] [Line: 931] 
VulkanRHI::vkCreateQueryPool(Device->GetInstanceHandle(), &PoolCreateInfo, VULKAN_CPU_ALLOCATOR, &QueryPool) failed, VkResult=-2
 at ./Runtime/VulkanRHI/Private/VulkanQuery.cpp:58 
 with error VK_ERROR_OUT_OF_DEVICE_MEMORY
Signal 11 caught.
Malloc Size=262146 LargeMemoryPoolOffset=262162 
CommonUnixCrashHandler: Signal=11
Malloc Size=131160 LargeMemoryPoolOffset=393352 
Malloc Size=131160 LargeMemoryPoolOffset=524536 
Engine crash handling finished; re-raising signal 11 for the default handler. Good bye.
Segmentation fault (core dumped)

Note: nothing in the project changed aside from being built in 5.1.1 instead of 5.0.3

What can I do to resolve this?

2 Likes