Applied-Software/ghostty
5
0
Fork 0
mirror of https://github.com/ghostty-org/ghostty.git synced 2025-07-22 19:56:08 +03:00
Code Issues Packages Projects Releases Wiki Activity

config: add cgroup memory limit config

Browse Source
This commit is contained in:
Mitchell Hashimoto
2024-06-05 10:27:53 -07:00
parent 3b41b89c23
commit 99d567274b
2 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/apprt/gtk/cgroup.zig
View File

@ -57,10 +57,11 @@ pub fn init(app: *App) ![]const u8 {
// of "max" because it's a soft limit that can be exceeded and // of "max" because it's a soft limit that can be exceeded and
// can be monitored by things like systemd-oomd to kill if needed, // can be monitored by things like systemd-oomd to kill if needed,
// versus an instant hard kill. // versus an instant hard kill.
// try internal_os.cgroup.configureMemoryLimit(transient, .{ if (app.config.@"linux-cgroup-memory-limit") |limit| {
// // 1GB try internal_os.cgroup.configureMemoryLimit(transient, .{
// .high = 1 * 1024 * 1024 * 1024, .high = limit,
// }); });
}
return transient; return transient;
} }

9
src/config/Config.zig
View File

@ -1012,6 +1012,15 @@ keybind: Keybinds = .{},
/// ///
@"linux-cgroup": LinuxCgroup = .@"single-instance", @"linux-cgroup": LinuxCgroup = .@"single-instance",
/// Memory limit for any individual terminal process (tab, split, window,
/// etc.) in bytes. If this is unset then no memory limit will be set.
///
/// Note that this sets the "memory.high" configuration for the memory
/// controller, which is a soft limit. You should configure something like
/// systemd-oom to handle killing processes that have too much memory
/// pressure.
@"linux-cgroup-memory-limit": ?u64 = null,
/// If this is false, then any cgroup initialization (for linux-cgroup) /// If this is false, then any cgroup initialization (for linux-cgroup)
/// will be allowed to fail and the failure is ignored. This is useful if /// will be allowed to fail and the failure is ignored. This is useful if
/// you view cgroup isolation as a "nice to have" and not a critical resource /// you view cgroup isolation as a "nice to have" and not a critical resource