Zed on Windows 11 aarch64 crashes on run (Arm64 - Snapdragon X Elite) #17374
Labels
bug
[core label]
open source
Open source community projects, contributions, etc
panic / crash
[core label]
platform support
An umbrella label for all platforms
windows
Check for existing issues
Describe the bug / provide steps to reproduce it
I have managed to compile Zed for Arm64 on Windows 11, but when running the compiled binary I get the following error:
[2024-09-04T21:12:21+02:00 ERROR fs.rs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
[2024-09-04T21:12:21+02:00 ERROR fs.rs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
[2024-09-04T21:12:21+02:00 ERROR fs.rs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
[2024-09-04T21:12:21+02:00 ERROR fs.rs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
[2024-09-04T21:12:21+02:00 ERROR blade_graphics::hal::init] No composite alpha flag for transparency: OPAQUE
Thread "main" panicked with "called 'Result::unwrap()' on an 'Err' value: ([0x0], ERROR_UNKNOWN)" at C:\Users\Ruben.cargo\git\checkouts\blade-b2bcd1de1cf7ab6a\fee06c4\blade-graphics\src\vulkan\pipeline.rs:520:18
0: backtrace::backtrace::dbghelp64::trace
at C:\Users\Ruben.cargo\registry\src\index.crates.io-6f17d22bba15001f\backtrace-0.3.73\src\backtrace\dbghelp64.rs:91
backtrace::backtrace::trace_unsynchronizedbacktrace::capture::impl$1::create::closure_env$0
at C:\Users\Ruben.cargo\registry\src\index.crates.io-6f17d22bba15001f\backtrace-0.3.73\src\backtrace\mod.rs:66
1: backtrace::backtrace::tracebacktrace::capture::impl$1::create::closure_env$0
at C:\Users\Ruben.cargo\registry\src\index.crates.io-6f17d22bba15001f\backtrace-0.3.73\src\backtrace\mod.rs:53
2: backtrace::capture::Backtrace::create
at C:\Users\Ruben.cargo\registry\src\index.crates.io-6f17d22bba15001f\backtrace-0.3.73\src\capture.rs:197
3: backtrace::capture::Backtrace::new
at C:\Users\Ruben.cargo\registry\src\index.crates.io-6f17d22bba15001f\backtrace-0.3.73\src\capture.rs:162
4: zed::reliability::init_panic_hook::closure$0
at C:\Users\Ruben\Downloads\zed\crates\zed\src\reliability.rs:58
5: alloc::boxed::impl$50::call
at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library\alloc\src\boxed.rs:2077
std::panicking::rust_panic_with_hook
at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library\std\src\panicking.rs:799
6: std::panicking::begin_panic_handler::closure$0
at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library\std\src\panicking.rs:664
7: std::sys_common::backtrace::__rust_end_short_backtracestd::panicking::begin_panic_handler::closure_env$0,never$
at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library\std\src\sys_common\backtrace.rs:171
error: process didn't exit successfully: 'target\debug\zed.exe' (exit code: 0xffffffff)
Environment
windows11 arm64 snapdragon
If applicable, attach your
~/Library/Logs/Zed/Zed.log
file to this issue.Zed.log
The text was updated successfully, but these errors were encountered: