Blade Vulkan pipeline crash on WoA w/ Snapdragon X1E80100

[Alonely0]

Check for existing issues

• Completed

Describe the bug / provide steps to reproduce it

I have compiled the latest tag on my Windows on ARM machine with the Snapdragon X Elite X1E80100, but upon running it, Blade panics with an ERROR_UNKOWN code. I have an inkling that it's because Blade does not support the Adreno GPU, but it's weird because there are compliant Vulkan drivers.
EDIT: Linked to this issue.

Environment

Zed version: v0.166.1
Zed channel: stable
OS: Windows 11 Home 24H2 10.0.26100.0
RAM: 16 GB
Architecture: aarch64

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.

2024-12-30T15:03:30.0376929+01:00 [INFO] ========== starting zed ==========
2024-12-30T15:03:30.1366808+01:00 [INFO] Use Segoe UI as UI font.
2024-12-30T15:03:30.1381054+01:00 [INFO] Opening main db
2024-12-30T15:03:30.1461859+01:00 [INFO] Opening main db
2024-12-30T15:03:30.1516964+01:00 [INFO] Using git binary path: None
2024-12-30T15:03:30.153496+01:00 [ERROR] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
2024-12-30T15:03:30.1814882+01:00 [INFO] No prompt template overrides directory found at C:\Users\guillem\AppData\Local\Zed\prompt_overrides. Using built-in prompts.
2024-12-30T15:03:30.1816899+01:00 [ERROR] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
2024-12-30T15:03:30.1857172+01:00 [INFO] Opening main db
2024-12-30T15:03:30.1892213+01:00 [ERROR] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
2024-12-30T15:03:30.1900067+01:00 [ERROR] Element not found. (0x80070490)
2024-12-30T15:03:30.1903419+01:00 [ERROR] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
2024-12-30T15:03:30.1904613+01:00 [ERROR] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
2024-12-30T15:03:30.2139461+01:00 [INFO] Enabling Vulkan Portability
2024-12-30T15:03:30.2666562+01:00 [INFO] Adapter: "Qualcomm(R) Adreno(TM) X1-85 GPU"
2024-12-30T15:03:30.2667691+01:00 [INFO] Ray tracing is supported
2024-12-30T15:03:30.2699571+01:00 [ERROR] No composite alpha flag for transparency: OPAQUE
2024-12-30T15:03:30.2700337+01:00 [INFO] Using surface present mode MAILBOX
2024-12-30T15:03:30.2700934+01:00 [WARN] Unable to forbid exclusive full screen
2024-12-30T15:03:30.2728558+01:00 [INFO] Creating a descriptor pool for at most 16 sets
2024-12-30T15:03:30.2730272+01:00 [INFO] Creating a descriptor pool for at most 16 sets
2024-12-30T15:03:30.2731776+01:00 [INFO] Initializing Blade pipelines for surface SurfaceInfo { format: Bgra8UnormSrgb, alpha: Ignored }
2024-12-30T15:03:30.2748971+01:00 [INFO] Skip function Some("to_tile_position")
2024-12-30T15:03:30.2751807+01:00 [INFO] Skip function Some("to_tile_position")
2024-12-30T15:03:30.6600398+01:00 [ERROR] {
"thread": "main",
"payload": "called Result::unwrap() on an Err value: ([0x0], ERROR_UNKNOWN)",
"location_data": {
"file": "C:\Users\guillem\.cargo\git\checkouts\blade-b2bcd1de1cf7ab6a\e142a3a\blade-graphics\src\vulkan\pipeline.rs",
"line": 546
},
"backtrace": [
"backtrace::backtrace::dbghelp64::trace",
"backtrace::backtrace::trace_unsynchronized",
"backtrace::backtrace::trace",
"backtrace::capture::Backtrace::create",
"backtrace::capture::Backtrace::new",
"zed::reliability::init_panic_hook::closure$0",
"alloc::boxed::impl$50::call",
"std::panicking::rust_panic_with_hook",
"std::panicking::begin_panic_handler::closure$0",
"std::sys::backtrace::__rust_end_short_backtracestd::panicking::begin_panic_handler::closure_env$0,never$"
],
"app_version": "0.166.1",
"release_channel": "Zed",
"os_name": "Windows",
"os_version": "10.0.26100",
"architecture": "aarch64",
"panicked_on": 1735567410660,
"system_id": "b5425a64-d2a4-4f99-a586-ec4bc8cb1a35",
"installation_id": "df9a5a4e-c260-47aa-9686-e0cb3023a8b4",
"session_id": "b1ac1fcb-5e9d-4920-8edd-2464bd6c9b4d"
}

[Alonely0]

The Blade dev seems to think this is a driver bug, so you may close this issue if you want.

[JosephTLyons]

@kvark - is there anything to address here?

[kvark]

This needs someone with access to the affected hardware to narrow down the shader code to the specific construct that makes the driver freak out (as described in kvark/blade#222 (comment))