26.2 Snapshot 1 - Vulkan Renderer crashes with exit code 11 (Segmentation Fault) on Linux using Mesa/RADV (OpenGL works fine)

The game crashes immediately after finishing texture atlas loading when the Vulkan graphics backend is used. The launcher shows a generic crash with exit code 11 (Segmentation Fault). This occurs with a clean installation of the snapshot (no mods).

Crucially, the game works perfectly when forcing the OpenGL backend (e.g., using -Dminecraft.forceOpenGL=true). The issue is strictly isolated to the Vulkan renderer.

Steps to Reproduce:
1. Install a clean instance of 26.2-snapshot-1 on a Linux system with an AMD GPU using the RADV (Mesa) driver.
2. Ensure no JVM arguments that force OpenGL are present (the snapshot defaults to the Vulkan backend).
3. Launch the game.
4. Observe the game load assets, display "Created: ...atlas" in the log, and then immediately crash with exit code 11.

Observed Behavior:
The game process terminates with exit code 11 (Segmentation Fault). The log shows the Vulkan backend initializing successfully, followed by the loading of assets (blocks.png-atlas, items.png-atlas, etc.), but the game window crashes before the main menu appears.

Expected Behavior:
The game should load to the main menu successfully using the Vulkan backend, just as it does when using the OpenGL backend.

Log Excerpts & Notes:
- Backend initializes without errors:
[Render thread/INFO]: Using graphics backend Vulkan, using drivers: 1.4.335 radv Mesa 26.0.4-arch2.2
- Crash occurs after texture atlas loading:
[Render thread/INFO]: Created: 512x512x0 minecraft:textures/atlas/shulker_boxes.png-atlas
- Launcher Output:
游戏进程崩溃了。退出代码：11。 (Game process crashed. Exit code: 11.)

Additional Context:
- OpenGL Workaround: Adding the JVM flag -Dminecraft.forceOpenGL=true completely resolves the crash, and the game runs normally.
- The missing libflite.so warning in the log is irrelevant to this crash (the narrator library failure is a known warning that does not cause a crash; exit code 11 is unrelated to text-to-speech).
- This appears specific to the RADV Vulkan driver. Users with NVIDIA proprietary drivers or amdvlk may not experience this.

Suspected Cause:
A memory access violation (Segfault) within the new Vulkan renderer when interacting with the RADV driver, possibly related to command buffer management or texture memory allocation specific to the Mesa driver stack.