Upstream software project

oomd

Userspace Out-Of-Memory (OOM) killer

About oomd

Userspace Out-Of-Memory (OOM) killer

This project links 4 native package records across 4 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

oomd repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.oomd: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
oomd
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
debian-12, debian-13, fedora-43, fedora-44
License expression
GPL-2.0-only
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Out of memory killing has historically happened inside kernel space. On a memory overcommitted linux system, malloc(2) and friends usually never fail. However, if an application dereferences the returned pointer and the system has run out of physical memory, the linux kernel is forced take extreme measures, up to and including killing processes. This is sometimes a slow and painful process because the kernel can spend an unbounded amount of time swapping in and out pages and evicting the page cache. Furthermore, configuring policy is not very flexible while being somewhat complicated. oomd aims to solve this problem in userspace. oomd leverages PSI and cgroupv2 to monitor a system holistically. oomd then takes corrective action in userspace before an OOM occurs in kernel space. Corrective action is configured via a flexible plugin system, in which custom code can be written. By default, this involves killing offending processes. This enables an unparalleled level of flexibility where each workload can have custom protection rules. Furthermore, time spent livedlocked in kernelspace is minimized.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. Package oomd

    bookworm (Debian 12 (Bookworm)) (admin): userspace Out-Of-Memory (OOM) killer for Linux systems

    0.5.0-1.2+b1: amd64 arm64

    Source: oomd

Debian 13 (Trixie)

  1. Package oomd

    trixie (Debian 13 (Trixie)) (admin): userspace Out-Of-Memory (OOM) killer for Linux systems

    0.5.0-1.2+b3: amd64 arm64

    Source: oomd

Fedora 43

  1. Package oomd

    43 (Fedora 43) (Unspecified): Userspace Out-Of-Memory (OOM) killer

    0.5.0-15.fc43: aarch64 x86_64

    Source: oomd

Fedora 44

  1. Package oomd

    44 (Fedora 44) (Unspecified): Userspace Out-Of-Memory (OOM) killer

    0.5.0-16.fc44: aarch64 x86_64

    Source: oomd

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.