mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2270] Memory Limit #1518
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1518
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @silgon on GitHub (Nov 23, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2270
Is there a way to limit the memory that a process uses with
firejail (0.9.56-LTS). I'm interested in using it with thunderbird. So maybe there is something to be written in the profile? I don't find any documentation about it.Also, in the man file, I found
RES Resident Memory Size (KiB), sandbox non-swapped physical memory. It is a sum of the RES values for all processes running in the sandbox.but I have no idea how or where to apply it.Thanks in advance.
@smitsohu commented on GitHub (Dec 5, 2018):
We have something in Firejail (
--rlimit-as), but not in the LTS version.As an alternative consider prlimit, it doesn't need any root privileges. The prlimit man pages fails to mention however that limits on RSS are without effect in contemporary kernels.
But something like
prlimit --as=50000000 firejailshould be possible.@chiraag-nataraj commented on GitHub (May 20, 2019):
@silgon, is this still an issue? Were you able to upgrade your firejail to take advantage of the feature?
@silgon commented on GitHub (May 20, 2019):
Sorry, I'm not using it anymore, so I couldn't tell. I'll close the issue for now. Thanks for the update. =)