On 22 Jul 2021, at 20:01, Richard Shaw <hobbes1069(a)gmail.com>
wrote:
I have a Kiosk I'm trying out using Chromium, unfortunately it seems to have a memory
leak and crashes in less than 24 hours of usage.
It likely that the problem is not a bug in chromium but rather the javascript that has
been run on the pages that where loaded. Tricks to cache images in memory and
other stuff that javascript code does leads to ever increasing memory foot print.
I see systemD has an option for "MemoryMax" but was wondering if anyone has
actually used it?
Is it as simple as
MemoryMax=512M
OnFailure=Restart
or something like that?
I used to work on a embedded system that had a web browser, WebKit based,
and it had to be limited with control groups as well.
What we did, I recall, is limit swap and memory for the slice that the browser ran in.
Also we configured the slice to set oom killer parameters.
If you do not do this you risk the oom killer killing the wrong process.
Have done this then oom killer will kill the process and systemd will restart it.
Barry
Thanks,
Richard
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
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/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure