Linux: TriOS 1.3.4 segfaults on exit (GTK window teardown / FlutterEngineRemoveView invalid arguments)

[ayeohx]

First of all, ChatGPT compiled this information for me and helped me run test. I don't understand any of it. Pasting below.

Title

Linux: TriOS 1.3.4 segfaults on exit (GTK window teardown / FlutterEngineRemoveView invalid arguments)

Description

TriOS launches and functions normally, but consistently segfaults when closing the application on Linux. The crash occurs during shutdown after the Flutter engine attempts to remove the view.

This happens every time the program exits.

Environment

TriOS version: 1.3.4

OS: Nobara Linux (Fedora-based)

Kernel: 6.19.8-200.nobara.fc43.x86_64

Desktop session: Wayland

GPU stack: Mesa 26.0.2

Reproduction

Launch TriOS from terminal:

cd ~/Games/TriOS
./TriOS

Close TriOS normally.

Application segfaults.

Terminal Output

Startup output:

../TriOS: /lib64/libcurl.so.4: no version information available (required by /home/ayeohx/Games/TriOS/lib/libsentry.so)

Gtk-WARNING: Error loading icon from file 'assets/images/telos_faction_crest.png'
Failed to open file: No such file or directory

Gdk-Message: Unable to load from the cursor theme
Initializing TriOS logging framework...
Crash reporting is disabled.
TriOS v1.3.4 logging started.
Platform: linux Linux 6.19.8-200.nobara.fc43.x86_64

Shutdown output:

embedder.cc (2575): 'FlutterEngineRemoveView' returned 'kInvalidArguments'. Remove view info was invalid. The implicit view cannot be removed.

WARNING: Failed to cleanup compositor shaders, unable to make OpenGL context current

Gtk-CRITICAL: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed
Gdk-CRITICAL: gdk_window_get_state: assertion 'GDK_IS_WINDOW (window)' failed

Segmentation fault (core dumped)
Stack Trace (top)
gtk_window_is_maximized
libwindow_manager_plugin.so
libflutter_linux_gtk.so
g_application_run
main

Full trace shows crash originating from:

method_call_cb
libwindow_manager_plugin.so
libflutter_linux_gtk.so
Additional Notes

Tests performed:

Forced software rendering:

LIBGL_ALWAYS_SOFTWARE=1 ./TriOS

Disabled GTK modules:

env -u GTK_MODULES GTK_THEME=Adwaita ./TriOS

Behavior unchanged — crash still occurs on exit.

This suggests the crash is likely happening during Flutter/GTK window teardown in the window_manager plugin, possibly when querying window state after the widget/window is already destroyed.

Impact

Functionality of TriOS appears normal while running, but the application segfaults every time it exits.