Main Branch - closing window causes segfault on Linux

[johnny-smitherson]

Here is an app

Cargo.toml

dioxus-native = { git = "https://github.com/DioxusLabs/blitz", rev = "4be7733", features = ["prelude"] }

src/bin/main2.rs

fn main() {
    dioxus_native::launch(App)
}

use dioxus_native::prelude::*;

#[component]
fn App()->Element {
    rsx! {
        h1 {
            "Hello"
        }
    }
}

Run it with

 RUST_BACKTRACE=full RUST_LOG=info cargo run --bin main2 

It opens. Then click x on the window. The process segfaults and the shell might hang.

fish: Job 1, 'RUST_BACKTRACE=full RUST_LOG=in…' terminated by signal SIGSEGV (Address boundary error)

---

Running on Linux hostname 6.19.3-2-cachyos #1 SMP PREEMPT_DYNAMIC Fri, 20 Feb 2026 01:02:58 +0000 x86_64 GNU/Linux - archlinux variant

Here are some core dumps
https://github.com/johnny-smitherson/native-core-dump

[nicoburns]

Is this X or Wayland?

[johnny-smitherson]

Wayland, yes. Here are some package versions

❯ sudo pacman -Syu --needed \
          atk cairo pango gdk-pixbuf2 libsoup3 webkit2gtk-4.1 alsa-lib gtk3 \
           xdotool openssl  \
          base-devel  \
          cmake freeglut libx11 libxmu libxi glu \
           sdl2
:: Synchronizing package databases...
 cachyos-v3 is up to date
 cachyos-core-v3 is up to date
 cachyos-extra-v3 is up to date
 cachyos is up to date
 core is up to date
 extra is up to date
 multilib is up to date
warning: at-spi2-core-2.58.3-1.1 is up to date -- skipping
warning: cairo-1.18.4-1.1 is up to date -- skipping
warning: pango-1:1.57.0-2.1 is up to date -- skipping
warning: gdk-pixbuf2-2.44.4-1.1 is up to date -- skipping
warning: libsoup3-3.6.6-1.1 is up to date -- skipping
warning: webkit2gtk-4.1-2.50.5-1 is up to date -- skipping
warning: alsa-lib-1.2.15.3-2.1 is up to date -- skipping
warning: gtk3-1:3.24.51-1.1 is up to date -- skipping
warning: xdotool-4.20251130.1-1.1 is up to date -- skipping
warning: openssl-3.6.1-1.1 is up to date -- skipping
warning: base-devel-1-2 is up to date -- skipping
warning: cmake-4.2.3-1.1 is up to date -- skipping
warning: freeglut-3.8.0-1.1 is up to date -- skipping
warning: libx11-1.8.13-1.1 is up to date -- skipping
warning: libxmu-1.3.1-1.1 is up to date -- skipping
warning: libxi-1.8.2-1.1 is up to date -- skipping
warning: glu-9.0.3-3.1 is up to date -- skipping
warning: sdl2-compat-2.32.64-1.1 is up to date -- skipping
:: Starting full system upgrade...
 there is nothing to do

[johnny-smitherson]

If relevant also on nvidia proprietary driver

❯ nvidia-smi 
Mon Feb 23 19:17:11 2026       
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 590.48.01              Driver Version: 590.48.01      CUDA Version: 13.1     |
+-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 3090        Off |   00000000:03:00.0  On |                  N/A |
|  0%   50C    P8             43W /  350W |    2888MiB /  24576MiB |     48%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

Let me know if I can send more debug info

[nicoburns]

I suspect we're dropping something in the wrong order. Or a ref-counting cycle is causing the Window not to be dropped at all.

Perhaps something like rust-windowing/winit#3379 (comment)

[niminypiminy]

The root cause on linux/wayland is that the runtime dies before the window context is fully detached. the driver attempts to access memory that has already been deallocated. I solved this exact issue a few months ago by initializing the runtime manually.

Example at the top of your main function initialize:

let runtime = Builder::new_multi_thread()
.worker_threads(4)
.enable_all()
.build()?;

and then the handle.block_on for graceful exit, or however you want to do it in your app should be after dioxus_native::launch_cfg at the very bottom of your function so cleanup runs after window is closed. This should resolve the SIGSEGV on your device.