ghostty crashed with SIGSEGV in gtk_widget_set_visible()

[alexander-potemkin]

Issue Description

Ghostty crashes when switching from Dark Style on Ubuntu 24.04 LTS

Crash information that feels important attached.

Reproduction Steps

1. Open Ghossty
2. Switch off Dark mode

Ghostty Version

Ghostty 1.1.3

Version
  - version: 1.1.3
  - channel: stable
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
  - desktop env: other
  - GTK version:
    build      : 4.14.2
    runtime    : 4.14.2
  - libadwaita : enabled
    build      : 1.5.0
    runtime    : 1.5.0
  - libX11     : enabled
  - libwayland : enabled

OS Version Information

Ubuntu 24.04.2 LTS

(Linux only) Display Server

Wayland

(Linux only) Desktop Environment/Window Manager

Gnome 46

Ghostty Configuration

cursor-invert-fg-bg = true
mouse-hide-while-typing = true
command = /bin/bash
copy-on-select = false
click-repeat-interval = 500
desktop-notifications = false
term = xterm-256color
auto-update-channel = stable

Additional Relevant Configuration

No response

I acknowledge that:

• I have reviewed the FAQ and confirm that my issue is NOT among them.
• I have searched the Ghostty repository (both open and closed Discussions and Issues) and confirm this is not a duplicate of an existing issue or discussion.

[pluiedev]

Could you try to reproduce this in a debug tip build and send the stacktrace here?

[alexander-potemkin]

Got it crashed again - switched to Development version to reproduce.
@pluiedev could you please, help me with the steps required once the crash reproduced on development / debug version? Would there be some file to send? Or something of the kind?

[pluiedev]

Copy over the log output and the stacktrace (which is the thing that spits out a lot of code tracing back to where the error occurred). If you can reliably reproduce the issue then recording an asciinema helps too.

[alexander-potemkin]

Copy over the log output and the stacktrace (which is the thing that spits out a lot of code tracing back to where the error occurred). If you can reliably reproduce the issue then recording an asciinema helps too.

Thank you. But where the log output and stacktrace would be placed?

The only thing I've seen them - STDERR/STDOUT - is it the only place and I've got to keep original Ubuntu terminal open to catch them?

[rhodes-b]

Yes run ghostty in a separate terminal then copy and paste the output here

[alexander-potemkin]

I'm sorry - debug version doesn't crash for a few days now.

I happened to have both debug and non-debug version running and non-debug version crashed, while debug version didn't.

The only thing I can say for sure - it's that 'production' version crashes quite reliably after working for ~8 hours, while Gnome theme change (at the end of the day / beginning of the day)

[alexander-potemkin]

At the times when it doesn't - if shows something like 'Configuration successfully updated' (or reloaded...)

That is the only additional thing I have noticed so far.

[mitchellh]

This is likely fixed with -ng (default on main). I can't reproduce it by switching light/dark but not sure if I ever could. We rewrote all our memory management in -ng for GTK so regardless this issue likely doesn't apply anymore. Please try latest and report back!

[alexander-potemkin]

Thank you! Yeah, I've read the news on GTK rework - waiting for the release impatiently!