Page MenuHomeSolus

Nohang Userspace OOM daemon
Closed, WontfixPublic

Description

Name of the software:
nohang

Project/product Homepage:
https://github.com/hakavlad/nohang

Why we should include this into the repository, i.e. what does it do that the alternatives do not?
OOM conditions may cause freezes, livelocks, drop caches and processes to be killed (via sending SIGKILL) instead of trying to terminate them correctly (via sending SIGTERM or takes other corrective action). Some applications may crash if it's impossible to allocate memory.

Alternatives include (No alternatives that I could find in the solus repository so these are just similar projects):
earlyoom (https://github.com/rfjakob/earlyoom) - More well known however less configurable and has not been updated for a few months
oomd (https://github.com/facebookincubator/oomd) - Less information available and driven by Facebook

Is it open source?
Yes - MIT License

If there are no upstream releases but the inclusion policy is otherwise met, please provide a link to the source repository (i.e. GitHub)
https://github.com/hakavlad/nohang
Latest commit as of writing this package request was September 29th 2019

Who and how many users do you anticipate will use this software?
I could see this being useful to many users however I don't believe it is a common tool to search for. Users this could be useful for in particular include:
Anyone working with large files - Loading a larger than expected file which consumes all the system memory bringing the system down requiring a reboot
Programmers - Kills a runaway process before it bring the whole machine down requiring a reboot
People who open lots a tabs - Can kill browser session instead of the whole machine locking up and requiring a reboot
etc.

Related Objects

Event Timeline

adurante created this task.Oct 29 2019, 2:05 PM

I get that we will want to have one of these at some point, but I have zero interest in a long-running python application. So nohang is out. earloom is promising but I need to see a little more movement.

Sure thing, I was originally going to write this request as being for "earlyoom" since I am not a very big fan of Python either however since it was less active I decided to write this for nohang.

Would it be preferable for you guys on the tracking side if you were to kill this task/request and I make a new one for earlyoom? I wouldn't mind if it is preferred.

ArjenR added a subscriber: ArjenR.Nov 1 2019, 8:14 PM

I run earlyoom but I cannot compare it to the other mentioned solutions. I chose earlyoom since it's only dependency is glibc, which might be more easy. However, I am a Python fan. Should checkout nohang too, I suppose.

ArjenR added a comment.Nov 1 2019, 9:28 PM

1st impressions:

  • sizewize it is larger than earlyoom.
  • it teminates / kills the real cuplrit in my tests better then earlyoom when there are multiple large programs loaded.

https://github.com/rfjakob/earlyoom/issues/129#issuecomment-563272191

Just dropping this, It seems earlyoom is still being actively maintained by the author and Pull Requests are still being accepted. I don't know if this counts as enough "movement" for the Solus Devs but wanted to drop this note anyway since I wasnt sure when I created this request if the package was being actively maintained or not.

https://github.com/rfjakob/earlyoom/issues/129#issuecomment-563272191
Just dropping this, It seems earlyoom is still being actively maintained by the author and Pull Requests are still being accepted. I don't know if this counts as enough "movement" for the Solus Devs but wanted to drop this note anyway since I wasnt sure when I created this request if the package was being actively maintained or not.

I'm not sure where you're getting the impression that "Pull Requests are still being accepted". They've had a patch open since October for something as basic as a README fix. The comment you referenced that is exactly that, just a comment saying PRs are welcome. There still hasn't been any work done since @DataDrake's original comment.

JoshStrobl closed this task as Wontfix.Jan 29 2020, 3:53 PM
refola added a subscriber: refola.Oct 5 2020, 7:21 AM

They've had a patch open since October for something as basic as a README fix. The comment you referenced that is exactly that, just a comment saying PRs are welcome. There still hasn't been any work done since @DataDrake's original comment.

Looks like earlyoom was unofficially dormant for half a year, but there are now 5 releases from this year at https://github.com/rfjakob/earlyoom/tags

Phantop added a subscriber: Phantop.EditedDec 24 2020, 4:59 PM

I'd also like to say that earlyoom has one open pull request now (ironically for a minor readme change) but had a release since refola's comment above and the latest commit is from 1 month ago. It seems to be active, albiet with the maintainers taking breaks (last commit and that PR are from the same date). I'd also be willing to maintain the Solus package if this is accepted.