* fix(preload): look up the native glibc symbol version first so wrapped calls never allocate
On x86 the first dlvsym lookup asked for GLIBC_2.17, which only exists on arm64. The failed lookup makes glibc allocate, which deadlocks when the first wrapped call happens inside a program's own allocator setup. Each architecture now asks for its base version first.
* fix(zram): start the page-out worker per request instead of keeping a thread in every process
Every process that loaded the session preload carried a resident zr-worker thread from its constructor on. Programs that check they are single-threaded before forking or before unshare(CLONE_NEWUSER) failed, for example Chromium's zygote, which could not start its GPU process.
The signal handler now starts the worker with a raw clone on a stack the preload maps itself. The worker makes only raw system calls and exits when no request is left, so starting it from the handler is safe and idle processes stay single-threaded. When the worker cannot be started, the process trims inline in small steps as before.
* fix(preload): start the page-out worker with the same clone flags as a thread
Programs that filter clone to the flag set threads use, as browser
sandboxes do, now accept the worker. The kernel clears the stack-busy
word and wakes waiters when the worker exits.
* fix(preload): page out inline in single-threaded and self-sandboxed processes
A process with one thread may be about to check that it is single-threaded
before fork or unshare, and a process that added a seccomp filter after it
started may trap system calls into its own handler. Neither gets a worker
thread now; both trim inline in small steps as before.
* fix(preload): check the signalled thread's own seccomp filters before starting the worker
Read Seccomp_filters from /proc/thread-self/status so a thread that installed its own filter
without TSYNC trims inline instead of calling clone under that filter, and fall back to the
inline path when the signal mask cannot be changed.
* test(preload): start parked threads with SIGURG already blocked
* test(preload): count only page-out workers when checking for leftover threads
* chore: consistent code branding
* fix: carry legacy overrides, queues and live sync rows across the rename
* fix: keep queued legacy overrides on a failed rename and separate merged queue entries
* fix: move zram page-out off signal thread
* fix: drain pending zram requests
* Time the async and inline page-out runs on the same workload
* fix(zram): keep pageout worker responsive under load
* test(zram): synchronize signal delivery before fixture shutdown
* test(zram): compare matched single-request timings
* test(zram): correct single request timing control
* test(zram): calibrate single request timing together
* test(zram): fail the timed run when the acknowledgement never arrives
* Add opt-in zRAM compression for the Steam client while a game runs
A "zRAM compression" toggle under Steam > Settings > Session, below
"Keep downloads running". Off by default, kept once set, and disabled
on devices without swap or with a kernel older than 5.4.
When on, the session watches for Steam's reaper. 20 s into a game the
client and its web helpers page their private anonymous memory out to
the device's zram with MADV_PAGEOUT from inside their own process
(libblsession zram.c, SIGURG), again every 5 minutes, and read every
swapped page back once the game exits. No root is needed: only a
process itself may do this without CAP_SYS_NICE. With the toggle off
nothing is installed or started.
RedMagic NP06J, Palworld: Steam's resident memory fell from ~1.7 GB to
~1.1 GB with ~560 MB in zram, available memory during play rose by
~0.5-0.8 GB, and ~2 MB was left in zram after the read-back.
* Turn zRAM compression on by default below 12 GB of RAM
Until the toggle is changed, it follows the device: on when the kernel
supports it and the device has less than 12 GB of RAM, read from the
advertised memory size on Android 14+ and from total memory before that.
Turning it off is kept.
---------
Co-authored-by: xXJsonDeruloXx <danielhimebauch@gmail.com>