[Bug] Kiosk chromium runs away at ~90% CPU, overloads node #36

Closed
opened 2026-06-16 11:19:11 +00:00 by lfg2025 · 1 comment
Owner

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)

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)
Author
Owner

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.

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.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lfg2025/archy#36
No description provided.