Ghostty crashes on image preview with `yazi` inside `tmux`. #4266

wklimowicz · 2025-01-01T10:58:01Z

wklimowicz
Jan 1, 2025

This is a fairly obscure bug because it's nested in tmux and yazi: Ghostty crashes without any error messages when previewing large images/pdf's inside yazi. The only config different from defaults is you need a higher than default max_width and max_height in yazi.toml.

# ~/.config/yazi/yazi.toml
[preview]
max_width = 1500 # Or some other higher number
max_height = 1500

To reproduce, set the config up as above, find a big image (or pdf), open tmux, open yazi, and hover over the image. Within half a second all instances of ghostty shut down.

This happens whether or not you have set -g allow-passthrough on in ~/.tmux.conf. It doesn't crash in the debug build, only slows down to a crawl.

You can tell as you increase the max_width/max_height that the delay through tmux is getting bigger, (up to a second or so), but beyond a certain point it just shuts down all instances of Ghostty in the release build. I think this is all to do with how the Kitty Graphics Protocol passes through, but I don't understand the internals well enough.

Fedora 41
Latest Build of Ghostty (1.0.2)

Attached the log from the release build:

Debug Logs

info: ghostty version=1.0.2-main+60611b8a
info: ghostty build optimize=ReleaseFast
info: runtime=apprt.Runtime.gtk
info: font_backend=font.main.Backend.fontconfig_freetype
info: dependency harfbuzz=8.4.0
info: dependency fontconfig=21402
info: renderer=renderer.OpenGL
info: libxev backend=main.Backend.io_uring
info(os): setlocale from env result=en_GB.UTF-8
info(gtk): GTK version build=4.16.5 runtime=4.16.5
info(config): creating template config file: path=/home/wojtek/.config/ghostty/config
warning(config): error creating template config file err=error.FileNotFound
info(config): default shell source=env value=/usr/bin/zsh
info(sentry): sentry envelope does not contain crash, discarding
info(gtk): libadwaita version build=1.6.2 runtime=1.6.2
EGL API version 1.5 found
 - Vendor: Mesa Project
 - Version: 1.5
 - Device: /dev/dri/renderD128, 226 128
 - Client APIs: OpenGL OpenGL_ES 
 - Extensions:
	EGL_ANDROID_blob_cache
	EGL_ANDROID_native_fence_sync
	EGL_EXT_buffer_age
	EGL_EXT_config_select_group
	EGL_EXT_create_context_robustness
	EGL_EXT_image_dma_buf_import
	EGL_EXT_image_dma_buf_import_modifiers
	EGL_EXT_pixel_format_float
	EGL_EXT_present_opaque
	EGL_EXT_query_reset_notification_strategy
	EGL_EXT_surface_compression
	EGL_EXT_swap_buffers_with_damage
	EGL_IMG_context_priority
	EGL_KHR_cl_event2
	EGL_KHR_config_attribs
	EGL_KHR_context_flush_control
	EGL_KHR_create_context
	EGL_KHR_create_context_no_error
	EGL_KHR_fence_sync
	EGL_KHR_get_all_proc_addresses
	EGL_KHR_gl_colorspace
	EGL_KHR_gl_renderbuffer_image
	EGL_KHR_gl_texture_2D_image
	EGL_KHR_gl_texture_3D_image
	EGL_KHR_gl_texture_cubemap_image
	EGL_KHR_image_base
	EGL_KHR_no_config_context
	EGL_KHR_reusable_sync
	EGL_KHR_surfaceless_context
	EGL_KHR_swap_buffers_with_damage
	EGL_KHR_wait_sync
	EGL_MESA_configless_context
	EGL_MESA_drm_image
	EGL_MESA_gl_interop
	EGL_MESA_image_dma_buf_export
	EGL_MESA_query_driver
	EGL_MESA_x11_native_visual_id
	EGL_WL_bind_wayland_display
	EGL_WL_create_wayland_buffer_from_image
 - Selected fbconfig: R8G8B8A8, depth 0, stencil 0
          high depth: R16G16B16A16 float, depth 0, stencil 0
Creating EGL context version 3.2 (debug:no, forward:no, legacy:no, es:no)
Using OpenGL backend EGL
Creating EGL context version 3.2 (debug:no, forward:no, legacy:no, es:no)
OpenGL version: 4.6 (core)
GLSL version: 4.60
Max texture size: 16384
Enabled features (use GDK_GL_DISABLE env var to disable):
    debug: ✓
    unpack-subimage: ✓
    half-float: ✓
    sync: ✓
    base-instance: ✓
    buffer-storage: ✓
OpenGL version: 4.6 (core)
GLSL version: 4.60
Max texture size: 16384
Enabled features (use GDK_GL_DISABLE env var to disable):
    debug: ✓
    unpack-subimage: ✓
    half-float: ✓
    sync: ✓
    base-instance: ✓
    buffer-storage: ✓
Creating EGL context version 3.3 (debug:no, forward:no, legacy:no, es:no)
OpenGL version: 4.6 (core)
GLSL version: 4.60
Max texture size: 16384
Enabled features (use GDK_GL_DISABLE env var to disable):
    debug: ✓
    unpack-subimage: ✓
    half-float: ✓
    sync: ✓
    base-instance: ✓
    buffer-storage: ✓
info(grid): loaded OpenGL 4.6
info(io_exec): found Ghostty resources dir: /home/wojtek/.local/share/ghostty
info(io_exec): shell integration automatically injected shell=termio.shell_integration.Shell.zsh
warning(gtk): unimplemented action=apprt.action.Action.Key.cell_size
warning(gtk): unimplemented action=apprt.action.Action.Key.size_limit
info(io_exec): started subcommand path=/bin/sh pid=68633
info(io_exec): subcommand cgroup=-
Creating EGL context version 3.2 (debug:no, forward:no, legacy:no, es:no)
OpenGL version: 4.6 (core)
GLSL version: 4.60
Max texture size: 16384
Enabled features (use GDK_GL_DISABLE env var to disable):
    debug: ✓
    unpack-subimage: ✓
    half-float: ✓
    sync: ✓
    base-instance: ✓
    buffer-storage: ✓
Using fractional scale 1 for EGL window (1122 722 => 1122 722)
info(grid): reallocating GPU buffer old=0 new=8
info(osc): unknown semantic prompts option: cl
warning(osc): invalid OSC command: 1337;SetUserVar=WEZTERM_PROG=
warning(osc): invalid OSC command: 1337;SetUserVar=WEZTERM_USER=d29qdGVr
warning(osc): invalid OSC command: 1337;SetUserVar=WEZTERM_IN_TMUX=MA==
warning(osc): invalid OSC command: 1337;SetUserVar=WEZTERM_HOST=VU5LTk9XTg==
warning(io_handler): OSC 7 host must be local
info(stream): OSC 1 (change icon) received and ignored icon=~
warning(stream): unimplemented OSC command: change_window_icon
warning(osc): invalid OSC command: 133;P;k=i
info(grid): reallocating GPU buffer old=8 new=20
Using fractional scale 1 for EGL window (2478 1408 => 2478 1408)
warning(osc): invalid OSC command: 133;P;k=i
info(grid): reallocating GPU buffer old=20 new=38
warning(osc): invalid OSC command: 133;P;k=i
warning(osc): invalid OSC command: 133;P;k=i
info(grid): reallocating GPU buffer old=38 new=65
warning(osc): invalid OSC command: 1337;SetUserVar=WEZTERM_PROG=Y2QgUGljdHVyZXM=
info(stream): OSC 1 (change icon) received and ignored icon=cd
warning(stream): unimplemented OSC command: change_window_icon
warning(stream): unimplemented OSC callback: terminal.osc.Command{ .end_of_command = terminal.osc.Command.Command__struct_96114{ .exit_code = 0 } }
warning(stream): unimplemented OSC command: end_of_command
info(osc): unknown semantic prompts option: cl
warning(osc): invalid OSC command: 1337;SetUserVar=WEZTERM_PROG=
warning(osc): invalid OSC command: 1337;SetUserVar=WEZTERM_USER=d29qdGVr
warning(osc): invalid OSC command: 1337;SetUserVar=WEZTERM_IN_TMUX=MA==
warning(osc): invalid OSC command: 1337;SetUserVar=WEZTERM_HOST=VU5LTk9XTg==
warning(io_handler): OSC 7 host must be local
info(stream): OSC 1 (change icon) received and ignored icon=~/Pictures
warning(stream): unimplemented OSC command: change_window_icon
warning(stream): unimplemented OSC callback: terminal.osc.Command{ .end_of_command = terminal.osc.Command.Command__struct_96114{ .exit_code = 0 } }
warning(stream): unimplemented OSC command: end_of_command
warning(osc): invalid OSC command: 133;P;k=i
warning(osc): invalid OSC command: 1337;SetUserVar=WEZTERM_PROG=dG11eA==
info(stream): OSC 1 (change icon) received and ignored icon=tmux
warning(stream): unimplemented OSC command: change_window_icon
warning(stream): unimplemented mode: 7727
warning(stream): unimplemented mode: 7727
warning(stream): unimplemented mode: 7727
info(grid): reallocating GPU buffer old=65 new=255
info(grid): reallocating GPU buffer old=255 new=390
info(grid): reallocating GPU buffer old=390 new=593
info(grid): reallocating GPU buffer old=593 new=3063
Gdk-Message: 10:47:42.896: Error flushing display: Resource temporarily unavailable

rhodes-b · 2025-01-01T16:06:17Z

rhodes-b
Jan 1, 2025

I think the key issue here is tmux. If it works just fine outside of tmux I think its unlikely a ghostty bug.

Tmux does not offically support kitty image protocol but set -g allow-passthrough on allows stuff to pass through to the terminal this is still a hack which can and will cause issues

5 replies

jcollie Jan 1, 2025
Collaborator

If a combination of user actions causes Ghostty to crash, it's a Ghostty bug. The main issue will be reproducability. A developer will need to be able to reproduce the problem in order to fix the issue.

@wklimowicz can you share the results of ghostty +version, your tmux config, your ghostty config and an image that causes the crash?

wklimowicz Jan 1, 2025
Author

`ghostty +version`

Ghostty 1.0.2-main+60611b8a

Version
  - version: 1.0.2-main+60611b8a
  - channel: tip
Build Config
  - Zig version: 0.13.0
  - build mode : builtin.OptimizeMode.ReleaseFast
  - app runtime: apprt.Runtime.gtk
  - font engine: font.main.Backend.fontconfig_freetype
  - renderer   : renderer.OpenGL
  - libxev     : main.Backend.io_uring
  - GTK version:
    build      : 4.16.5
    runtime    : 4.16.5
  - libadwaita : enabled
    build      : 1.6.2
    runtime    : 1.6.2
  - libX11     : enabled

ghostty config can be default.

`tmux`

Can be left blank, but also crashes with this which is related to how tmux works with graphics:

# ~/.tmux.conf
set -g allow-passthrough on

`yazi`

This is important, since the default width/height didn't cause crashes for me, only slowdowns:

# ~/.config/yazi/yazi.toml
[preview]
max_width = 1500 # Or some other higher number
max_height = 1500

Example image

using magick, but any large-ish image or pdf will do:

magick -size 800x800 xc:white white.png

Other terminals

I forgot to mention that this works perfectly fine in kitty, so in principle it's possible. It works on windows terminal but through sixel I believe. Other terminals (gnome-terminal, ptyxis, alacritty) display a corrupted image but don't crash. Wezterm crashes.

rhodes-b Jan 1, 2025

Can you also share what Distro and window manager / desktop environtment you are using

jcollie Jan 1, 2025
Collaborator

Yeah we treat Kitty as the "gold standard" when it comes to the Kitty Image Protocol. Well, that and crashes are pretty much unacceptable.

wklimowicz Jan 1, 2025
Author

This is on:

Fedora 41
Gnome 47.2
WM: Mutter (Wayland)
tmux 3.5a
Yazi 0.4.2

Chrispycode · 2025-01-01T18:25:01Z

Chrispycode
Jan 1, 2025

The yazi documentation suggests two more options for the image preview, with them yazi does not crash for me.

set -ga update-environment TERM
set -ga update-environment TERM_PROGRAM

https://yazi-rs.github.io/docs/image-preview#tmux

2 replies

prurigro Jan 2, 2025

Ghostty still crashes when I try to run timg with these parameters set

Chrispycode Jan 5, 2025

yes after working with ghostty regularly it happened again, it feels random sometimes it works and sometimes it crashes on every image.
This also happens sometimes when I use chafa in tmux with the kitty graphics protocol.

arilebedey · 2025-01-02T12:32:29Z

arilebedey
Jan 2, 2025

1 reply

arilebedey Jan 2, 2025

I actually have a different issue altogether where yazi crashes on launch unless I run tmux kill-server after booting up. Sorry if there was any confusion.

prurigro · 2025-01-02T21:45:39Z

prurigro
Jan 2, 2025

Edited:

Testing timg yesterday, ghostty + tmux didn't crash when rendering smaller images, and did crash when rendering larger ones. Today I attempted to test again and somehow every image was output correctly: small, large, grids (which also crashed ghostty yesterday). I quit ghostty and started it back up with a fresh instance of tmux and now the crashes are occurring again...

8 replies

prurigro Jan 3, 2025

@rhodes-b: I just built a debug build of 1.0.1 and am still getting the crash. I did have every image work that one time on that note and I'm still not sure what was different about it...

@wklimowicz are you running your own debug build when it works for you or the official one for macos?

wklimowicz Jan 3, 2025
Author

I'm using my own build in Fedora running zig build -p $HOME/.local, without the -Doptimize=ReleaseFast flag.

rhodes-b Jan 3, 2025

@rhodes-b: I just built a debug build of 1.0.1 and am still getting the crash. I did have every image work that one time on that note and I'm still not sure what was different about it...

Can you share the stack trace then?

prurigro Jan 3, 2025

So it doesn't seem like any of my crashes showed up in coredumpctl. I tried building the debug version again to see if I could coax one out (I'd flipped back to release after the last test), and now the crash doesn't occur; instead, the terminal window locks up and starts spamming this text (in the parent terminal that launched it):

debug(terminal): c=305 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=6E0 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=305 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=6E0 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=1DDE grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=305 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=305 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=6E1 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=305 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=6E1 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=1DDE grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=305 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=305 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=6E2 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=305 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=6E2 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=1DDE grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=305 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=305 grapheme attach to left=1 primary_cp=10EEEE
debug(terminal): c=6E4 grapheme attach to left=1 primary_cp=10EEEE

prurigro Jan 4, 2025

I tried running the non-debug version from another terminal to catch the output.

The first time I tried the image actually loaded correctly, but the log spammed >100 warning(grid): missing image for virtual placement, ignoring image_id=3166864385 with info(page_list): adjusting page capacity=terminal.page.Capacity{ .cols = 179, .rows = 259, .styles = 128, .hyperlink_bytes = 192, .grapheme_bytes = 262144, .string_bytes = 2048 } a single time.

The second time was a crash, and the error message was Gdk-Message: 14:00:07.098: Error flushing display: Resource temporarily unavailable

prurigro · 2025-02-11T16:39:49Z

prurigro
Feb 11, 2025

Just tested the latest version and the crash is still happening

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Ghostty crashes on image preview with `yazi` inside `tmux`. #4266

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 5 comments 16 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

Ghostty crashes on image preview with yazi inside tmux. #4266

Replies: 5 comments · 16 replies

jcollie Jan 1, 2025 Collaborator

wklimowicz Jan 1, 2025 Author

ghostty +version

tmux

yazi

Example image

Other terminals

jcollie Jan 1, 2025 Collaborator

wklimowicz Jan 1, 2025 Author

wklimowicz Jan 3, 2025 Author

Ghostty crashes on image preview with `yazi` inside `tmux`. #4266

Replies: 5 comments 16 replies

jcollie Jan 1, 2025
Collaborator

wklimowicz Jan 1, 2025
Author

`ghostty +version`

`tmux`

`yazi`

jcollie Jan 1, 2025
Collaborator

wklimowicz Jan 1, 2025
Author

wklimowicz Jan 3, 2025
Author