Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

16
  • 3
    Hi, the last option seems very interesting. Do I have to apply the systemd-run options to all Firefox "child processes" (e.g. WebExtensions and Web Content) or is it sufficient to limit the main process (firefox-bin)? Commented Aug 10, 2020 at 15:35
  • Also, will this option take care if there are multiple instances (e.g. there are usually 2-3 instances of WebExtensions)? And is the syntax for systemd-run case-sensitive, i.e. will it still work if I do systemd-run --scope -p MemoryLimit=500M webextensions for WebExtensions? Thx a lot ^-^ Commented Aug 10, 2020 at 15:55
  • PS.: Btw, what would be the syntax to apply the options to multiple processes? Would this work: systemd-run --scope -p MemoryLimit=200M firefox-bin MemoryLimit=200 WebExtensions MemoryLimit=500M Web Content (and do I need to escape blank spaces)? Commented Aug 10, 2020 at 16:09
  • 1
    Doing systemd-run --scope -p MemoryHigh=500M /opt/firefox/firefox opened a new Firefox window - is this setting permanent or do I have to open Firefox every time using the command? Commented Aug 10, 2020 at 22:18
  • 1
    What happens if the process attempts to write to more memory than the limit? Does Firefox try to minimize its usage automatically or does it just crash? Commented Jun 15, 2022 at 19:50