https://bugs.kde.org/show_bug.cgi?id=480884
--- Comment #4 from fanzhuyi...@gmail.com --- (In reply to Massimiliano L from comment #2) > Thank you for the answer. But this occurs systematically and does not occur > with GNOME Terminal. So there should be something in the design or behavior > of Konsole that triggers the OOM killer to terminate it together with the > child process. Any ideas on why this may be? > > If this is "not a bug" can we turn this into a wishlist item? I believe it > can significantly impact the user experience in some cases, putting Konsole > (and KDE software) behind competitors. > > It could be also interesting to understand whether this is distro-related. > If people not using Fedora are not experiencing the same issue, I may file a > bug report with Fedora as well. In general, the advice is to *not* operate your system in settings that frequently trigger the OOM killer. There are several ways to do that: - limiting the ram of memory-hungry processes (e.g., using systemd, or options to jvm) - use swap (zram offers a way to put swap inside ram, and you could always configure swap on harddrives) - upgrade your hardware If you must operate near regimes that saturate the memory, my suggestion is to custom configure an OOM killer, so you get more control over what is killed in OOM situations. The systemd and kernel OOM killers both use some sort of heuristics to decide which application to kill first. It is very hard for us to guarantee that konsole is not killed first -- in some cases, it might even be desirable to kill konsole first if more critical applications can continue. -- You are receiving this mail because: You are watching all bug changes.
