[Bug] Kiosk chromium runs away at ~90% CPU, overloads node #36
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
On .198 the kiosk display chromium was pinned at ~92% CPU (multiple procs), driving load to 8-10 and starving everything — including LND RPC (caused the receive-address Request timeout originally mis-attributed to bitcoin IBD) and podman image builds. Killing chromium drops load; it respawns on reboot. Investigate why the kiosk browser runs away (stuck page / GPU / reload loop) and cap/ànle it. (Found 2026-06-16 on .198)
Fixed (commit
45ac9be9): CPUQuota/MemoryMax cap on archipelago-kiosk.service + drop --enable-gpu-rasterization when no /dev/dri (headless spin), + bootstrap OTA self-heal. Kiosk disabled on .198 for now. Ships in v1.7.98.