Hi everyone,
I’ve been experimenting with Plasma Mobile on my PinePhone (and a testing VM) lately, and I’m encountering a persistent issue where the shell (kwin_wayland) becomes unresponsive or crashes back to the login screen under specific script execution loads.
I’m currently trying to automate some in-game testing on an Android container within the environment. I’ve been using free delta scripts to handle some of the Blox Fruit grinding and execution tasks, but I’ve noticed that as soon as the executor starts hitting high-frequency cycles, the Plasma shell’s resource management seems to struggle. The UI elements start to flicker, and eventually, the whole session hangs.
I’m trying to figure out if this is a known conflict with how Wayland handles input injection from background processes or if there’s a memory leak in how the mobile shell interacts with third-party executors. Has anyone else here noticed instability when running heavy script environments alongside the mobile session? I’ve checked the journalctl logs, and it seems like a segmentation fault in the compositor, but I’m not sure if I should be tweaking the OOM (Out of Memory) killer settings or if there’s a way to isolate these scripts from the main shell process better.
If anyone has experience debugging script-heavy workloads on KDE Mobile or knows of a specific Wayland protocol that might be causing this hang, I’d love to hear your thoughts. I really want to keep using Plasma as my main mobile environment, but the stability issues during these sessions are a bit of a dealbreaker.
Thanks!