KhronosGroup / KhronosGroup/Vulkan-Utility-Libraries

Validation layer trigger segment fault when create instance on ubuntu 22.04

Open
#234 3 comments 0 reactions 1 assignee View on GitHub

@christophe-lunarg is already working on this.

Since May 20, 2025.

bug enhancement Layer Settings OS - Platform Independent P1
Dominant language
C++
Stars
104
Forks
49
Avg merge
7h 15m
Merged PRs (30d)
4

Description

Environment:

  • OS: Ubuntu 22.04.4 LTS
  • GPU and driver version: Intel Corporation AlderLake-S GT1 (rev 0c) i915
  • SDK or header version if building from repo: ef846ac0883cde5e69ced0e7d7af59fe92f34e25
  • Options enabled (synchronization, best practices, etc.): VK_LAYER_KHRONOS_validation

Describe the Issue

When enable the vulkan validation layer, the vulkan program will crash because a segmentation fault inside the vulkan validation layer(to be more specific, the Vulkan-Utility-Libraries it used):
image

The segmentation fault happens when try to convert a std::string to std::filesystem::path.
After a quick investigation, it seems this bug is related to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90050

Expected behavior

program should not crash.

Valid Usage ID
No valid usage ID.

Additional context

Local g++ version:

g++ (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

The validation layer is built by

cmake -S . -B build -D UPDATE_DEPS=ON -D BUILD_WERROR=ON -D BUILD_TESTS=ON -D CMAKE_BUILD_TYPE=Debug
cmake --build build --config Debug

The program I run is:

export VK_INSTANCE_LAYERS=VK_LAYER_KHRONOS_validation
./my_vulkan_program

Then to know the backtrace I build the validation layer from source code, and then run

export VK_LAYER_PATH=/path_to_/Vulkan-ValidationLayers/build/layers
export VK_INSTANCE_LAYERS=VK_LAYER_KHRONOS_validation
./my_vulkan_program

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.