The412Banner be6c875277 Session stop: kill guest processes proot lost, and cap the session log ...

Twice today a session's Xwayland aborted from one thread ("The futex
facility returned an unexpected error code"), proot lost the tracee, and
the process lived on reparented to init: proot's seccomp filter, with no
tracer left, answers ENOSYS, so Xwayland's main loop logged
"WaitForSomething(): poll: Function not implemented" until something killed
it - 9 GB after Dolphin, 13 GB after PPSSPP. --kill-on-exit and the tree
sweep only reach what proot still traces, and the straggler sweep ran only
at the next session's start.

Now a session stop also kills every process of ours whose executable lives
in the Linux runtime, and bannerlator-session keeps only the first
BL_LOG_CAP bytes (256 MB) of session.log, draining the rest so a writer
that filled it is not killed by SIGPIPE.

2026-09-27 16:52:51 -04:00

..

desktop

Cemu (Wii U) from the front end and the desktop, and two session fixes

2026-09-27 16:30:49 -04:00

overlay/usr

Session stop: kill guest processes proot lost, and cap the session log

2026-09-27 16:52:51 -04:00

preload

Steam updates: the client is not uid 0 in the session - drop that test

2026-09-26 16:10:11 -04:00