#5665 [GUI] Heavy typing lag inside the app window only; same UI smooth in browser (0.2.12, Wayland)
open · @ralfdrewes · 4 commentaires · Sur GitHub
Description
# Strata desktop app (Linux): massive text-input lag inside the app window only **App:** Strata 0.2.12 (AppImage, Linux amd, rx9070 build) · **Control/engine:** current feed versions (engine 0.1.58) **OS/desktop:** Arch-based (CachyOS), kernel 7.3.1, KDE Plasma 6 on Wayland **GPU:** AMD RX 9070 (gfx1201) as compute card + integrated AMD GPU driving the desktop ## Symptom Typing into the chat input of the Strata desktop window is massively laggy — keystrokes are echoed hundreds of ms late / dropped behind the caret. This happens in **every** app window, including a brand-new, empty chat. ## Evidence it is the app window, not the serving stack * Opening the **same UI in a regular browser** via `http://127.0.0.1:<ui-port>/` while everything else runs: typing is perfectly smooth. Same server, same UI code. * Engine log during a typed burst: **no requests at all** (engine fully idle), so no generation is competing for CPU. * System was otherwise idle while typing: ~11 GiB RAM free, swap untouched, no indexer, no runaway process; the only CPU spikes ever seen coincide with active generation. * The problem appeared after updating the desktop app 0.2.10 → 0.2.12 on 2026-11-09 (update flow itself completed cleanly). System WebKitGTK (webkit2gtk-4.1 2.54.2) has not been updated this week; KDE/Qt likewise untouched for months. ## Things ruled out * Conversation size: new small chat window lags identically. * AMD DMABUF renderer path under Wayland: launching the AppImage with `WEBKIT_DISABLE_DMABUF_RENDERER=1` — **no improvement**. * Accessibility bridge spam: journal shows recurring `atk-bridge: get_device_events: ersetzt durch 'org.a11y.registry.getdeviceevents'` warnings from the WebKitWebProcess, but `toolkit-accessibility` is off and zero such warnings appeared during a laggy typing burst, so it looks like startup noise. * Model/engine/GPU: browser path proves the server side is unaffected. ## Environment note The machine hosts a 32 GB model in RAM/VRAM with ~113/125 GiB resident; could high memory residency influence the WebKitGTK window (e.g. via memory-pressure / madvise behaviour) while the browser process handles it fine? Just wondering, not claiming. ## Expected behaviour Typing in the app window should feel the same as in the browser. ## Asks 1. Any known WebKitGTK input-latency issue on Plasma 6 / Wayland with the bundled webview? 2. Would a toggle for an alternative renderer/window backend (or an officially supported "use my browser" mode) be an option in a future build? 3. Happy to test debug builds or env-var combinations (currently tried: DMABUF off).
Sur le site
Liens install, modèles, releases.