- Shipped
- September 28, 2026 at 8:25 PM UTC
- Author
- Kamo
- Commit
- 75de0f8
A page still drawing when the sleep image is written made the wake take minutes. SP11 Task 30's workstation slept with Kamo's sign-in page open (a full-screen zoom with an animated grayscale filter, ~1.2 vCPU under software rendering) and woke in 9 min 19 s: both vCPUs flat out for eight minutes, no disk I/O, ext4's journal blocked. One that slept with an idle desktop woke in 54 s. The restored kernel's scheduler clock (kvm-clock) starts over in the new VM, so until it passes its old value no thread is charged for its CPU and a busy one is not preempted. - Before hibernating, the AI profile minimizes every window on the desktop (a hidden Chrome page draws nothing and its timers are throttled), bounded to 10 s inside the sleep request; they stay minimized after the wake. - The AI's Chrome runs with --force-prefers-reduced-motion, which stops that page's animation for good. SP98 Task 16.