Segfault on macOS Tahoe (26.0)

[George9000]

What Operating System(s) are you seeing this problem on?

macOS

Which Wayland compositor or X11 Window manager(s) are you using?

No response

WezTerm version

20250909-070512-bf9a2aee

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

While using the helix editor in wezterm, on two occasions there's been a wezterm segfault.

Details here.

To Reproduce

No response

Configuration

In this gist.

Expected Behavior

No response

Logs

No response

Anything else?

No response

[bew]

Hello, does the crash also happen without your config ? Please provide any logs that appear when you run wezterm from another terminal.

If you have a way to reproduce the issue it would help any debugging to record what the programs are sending to wezterm using wezterm record

(also, note that in your config you forgot the config. before the front_end & max_fps options)

[George9000]

Thanks for the response. I launched wezterm from macOS Terminal with wezterm -n; since it was stable, I also tried with my config after correcting it as pointed out above. It remained stable without crashing. The only log messages that appeared were as follows:

12:29:52.193 wezterm-gui[2423:49108] error messaging the mach port for IMKCFRunLoopWakeUpReliable
16:58:16.358  WARN   wezterm_gui::termwindow::resize > cannot resize window to match Some(RowsAndCols { rows: 82, cols: 299 }) because window_state is FULL_SCREEN
16:58:17.544  WARN   wezterm_gui::termwindow::resize > cannot resize window to match Some(RowsAndCols { rows: 82, cols: 318 }) because window_state is FULL_SCREEN

I will follow-up if the issue recurs.

[Nymphium]

I also encountered the segfault with the same wezterm version, but Sequoia 15.6.1, M3 Pro 🙌

[n-kort]

I'm on Sequoia but this crashes wezterm every time:

1. open wezterm
2. open the Apple Device Simulator
3. take a screen recording of that device (not a screengrab)
4. when the floating recording appears, grab it (as if moving to a directory etc)
5. drag that over any part of a wezterm window
6. immediate crash

System Integrity Protection: enabled

Crashed Thread:        0  main  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes:       0x0000000000000001, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [39286]

When dragging a screengrab instead it just pastes the temporary file path. Using the wezterm -n suggestion above, the Terminal session shows:

2025-11-11 15:03:05.797 wezterm-gui[43962:62404557] Couldn't get a copy of a URL-flavored data from the pasteboard.
2025-11-11 15:03:05.798 wezterm-gui[43962:62404557] Looked for URLs on the pasteboard, but found none.
[1]    43962 segmentation fault  wezterm -n

[bigduu]

Got same issue