Linux AppImage: backend blocks system suspend (stuck in D state on FUSE page fault, freeze timeout after 20 s)

Offen
#39,682 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
38/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
linux, typescript

Rechercherichtung

Start in apps/desktop and trace how the Linux AppImage launches the backend process and handles system sleep. The report points to the backend binary running from a FUSE mount and a suspend freeze timeout, but does not identify an implementation entry point or a confirmed fix. First check how the app handles PrepareForSleep and review the existing AppImage packaging options; done means suspend and hibernation complete without the backend blocking the system freeze.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Before submitting
  • I searched existing issues. Closest are #38568 (SIGBUS after AppImage mount teardown) and #29636 (relaunches retaining FUSE mounts); neither covers suspend.
Area

apps/desktop (Linux AppImage)

Steps to reproduce
  1. Run the Linux x86_64 Nightly AppImage (FUSE-mounted, not extracted) on Omarchy/Hyprland.
  2. Leave it running, then suspend the machine (systemctl suspend, s2idle).
  3. Not deterministic: it happened once here while the app was idle in the background.
Expected behavior

The system freezes user space and suspends normally.

Actual behavior

The kernel cannot freeze the T3 Code server process. It sits in uninterruptible sleep (state D) on a page fault into its own binary, which lives on the AppImage FUSE mount. The suspend attempt is aborted after the 20 s freeze timeout; the screen looks hung for those 20 s. systemd retried and the second attempt succeeded.

PM: suspend entry (s2idle)
Filesystems sync: 0.062 seconds
Freezing user space processes
Freezing user space processes failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0):
task:t3code          state:D stack:0     pid:13387 tgid:13387 ppid:13124  task_flags:0x400000 flags:0x00080002
Call Trace:
 <TASK>
 __schedule+0x40f/0x1780
 ? page_cache_ra_order+0x3b1/0x410
 io_schedule+0x57/0xf0
 filemap_fault+0x9b7/0x1ba0
 ? __pfx_wake_page_function+0x10/0x10
 __do_fault+0x34/0x170
 do_read_fault+0x42/0x200
 ? pte_offset_map_rw_nolock+0x1f/0x90
 __handle_mm_fault+0xd12/0x1070
 ? do_syscall_64+0xaa/0x630
 handle_mm_fault+0xe7/0x2c0
 do_user_addr_fault+0x357/0xc20
 exc_page_fault+0x90/0x1c0
 asm_exc_page_fault+0x26/0x30
 </TASK>
OOM killer enabled.
Restarting tasks: Starting
Restarting tasks: Done
PM: suspend exit

PID 13387 is the backend: /tmp/.mount_T3-Cod…/t3code --require …/compileCache.cjs …/apps/server/dist/bin.mjs. Its text segment is mapped from /tmp/.mount_T3-Cod…/t3code.

Likely mechanism: the AppImage runtime (the FUSE daemon serving the squashfs) is frozen first. Then a page fault in the backend waits on a FUSE read that can no longer be answered, so the faulting task cannot reach the freezer. This is a known FUSE + suspend interaction. It also affects hibernation, which uses the same freeze step.

Possible mitigations:

  • Ship or recommend an extracted install (--appimage-extract, a .deb/.rpm/AUR package) so the binary is not backed by FUSE.
  • Have the backend hold an inhibitor and quiesce on PrepareForSleep, so it does not fault in new pages while the freeze is in progress.
Environment
  • T3 Code 0.1.11-nightly.20261118.4877, Linux x86_64 AppImage
  • Omarchy 4.5.0 (Arch), Hyprland, kernel 7.2.15, systemd 262
  • Intel Core Ultra 5 226V (Lunar Lake), btrfs on LUKS
Vorherrschende Sprache
TypeScript
Sterne
24.8k
Forks
6.4k
Ø Merge
4 Std. 29 Min.
Gemergte PRs (30 T.)
488

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus pingdotgg/t3code

Alle Issues in pingdotgg/t3code

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.