Let's keep this desktop-focused, since the proposal does not affect
Server edition.
On Sat, Jan 4, 2020 at 12:48 pm, drago01 <drago01@xxxxxxxxx> wrote:
As for the desktop case the running web browers in a cgroup to keep
them in check would solve most real world problems - other common
desktop apps don't use enough memory to cause such issues (unless
your system is really memory constrained but then the "buy more
memory" solution is the better fix).
The last time I saw my desktop hang due to a web browser using too much
memory was 2015.
The freezes I've encountered in the past five years were all related to
software development:
* When compiling large software projects, it's possible to run out of
RAM either when building lots of files in parallel, or when linking
* GNOME Builder runs ctags, and ctags likes to use dozens of GB of RAM
to index large software projects. I think it sometimes gets into a loop
where it just allocates more and more RAM until the desktop dies
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
