https://bugs.kde.org/show_bug.cgi?id=521467
Bug ID: 521467
Summary: elisa gets OOM-killed and takes down the entire shell
Classification: Plasma
Product: plasma-mobile
Version First unspecified
Reported In:
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Shell
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
Created attachment 193152
--> https://bugs.kde.org/attachment.cgi?id=193152&action=edit
journal log of the issue on bonito with 6.18.33-sdm670
DESCRIPTION
It's understood that elisa audio player can have a big memory footprint, as it
needs to manage a database of media files. It's agreed that the kernel could
end up killing elisa in out-of-memory conditions. But this should not kill the
entire shell, forcing the user to reboot the device.
E.g. I've seen koko's image editor getting OOM-killed as well, without further
effects.
I've noticed this on a google-bonito (sdm670, 3.5GiB RAM) but also on an
op6-enchilada (sdm845, 5.4GiB RAM): in the first days of usage, elisa runs
fine, then it triggers the kernel to OOM-kill it, that takes down the entire
shell.
Do we have any chance to mitigate this issue, to preserve the shell from
getting killed? E.g. adjusting the oom_score of processes that are required to
keep shell alive...
STEPS TO REPRODUCE
1. launch elisa
2. see the shell getting killed and the screen getting back to the framebuffer
OBSERVED RESULT
Elisa gets killed due to out-of-memory situation and the shell gets killed as
well.
EXPECTED RESULT
App gets killed, shell being preserved from the OOM issue.
SOFTWARE/OS VERSIONS
Operating System: Mobian testing/forky (issue seen both with 6.18.33-sdm670 and
7.1~rc7-sdm845)
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
--
You are receiving this mail because:
You are watching all bug changes.
