|
After a 33-minute suspend the desktop shell sat at ~45% of a core: its
main thread ran flat out for about a second every two seconds, in step
with the Perf 2s timer. Stack samples were almost all QV4 GC
(GCStateMachine::transition, MarkStack::drain) entered from allocData via
tryForceGCCompletion, under the regex loop in Perf.vram(), a 177-line
parse that should take microseconds. The main thread also posted ~1000
events a second to its own eventfd, against a few dozen in the other
shells. Reading: Qt 6.11's incremental collector, the default since 6.8,
never completed a cycle after resume, so every allocation forced a full
mark.
QV4_GC_TIMELIMIT=0 is Qt's documented switch back to non-incremental
collection. With it, after a 31-minute suspend the shell stayed at 0.3%
and ~37 wakeups a second. The live autostart.lua sets it too; keep the
two in step.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
|
The volume OSD drew only its "Output 72%" label, with the icon, bar and
device line clipped below the panel edge. The code and the theme were
not at fault: a hot reload fixed it, and a debug line logged just after
showed the volume row laid out correctly at the top of the panel. The
stuck state lived in the running process, so the fix is a restart.
quickshell has no reload subcommand and no IPC target for it, and a
hot reload needs a real content change to a file. reload.sh kills and
restarts each named component, or every directory holding a shell.qml,
and prints the qs count afterwards, since the process is qs and not
quickshell.
It must run from the user's terminal. A detached qs started from an
agent's tool call dies with the call, which would leave the desktop
without its shells; AGENTS.md now says so under Reloading.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
