> So there are already couple of low memory deamons. How's your different?
As mentioned in the text, it "will shoot off signals to interested user-space applications". It's targeted at "traditional" Linux desktops, like GNOME and everything else I work on.
Really looking forward to this. I often hit OOM when working with large files in Blender VSE, Inkscape, Scribus or GIMP. Most of the time when these things happen, they happen unpredictably. But if it's interesting, I can try to help with finding reproducible cases - I think partly some of them is OOM related, partly some of them is related to operations blocking the UI thread...
22 August 2019 at 05:40
I'll soon be flying to Greece for GUADEC but wanted to mention one of the things I worked on the past couple of weeks: the low-memory-monitor project is off the ground, though not production-ready.
low-memory-monitor, as its name implies, monitors the amount of free physical memory on the system and will shoot off signals to interested user-space applications, usually session managers, or sandboxing helpers, when that memory runs low, making it possible for applications to shrink their memory footprints before it's too late either to recover a usable system, or avoid taking a performance hit.
"low-memory-monitor: new project announcement"
6 Comments -
I think some applications, which could fast save one's state to disk, can save it's state and exit. Of course, in case of small free memory amount.
21 August 2019 at 13:04
That's already what the GLib API advises in the API documentation.
21 August 2019 at 13:14
Sound interesting.
21 August 2019 at 19:34
So there are already couple of low memory deamons. How's your different?
21 August 2019 at 19:41
> So there are already couple of low memory deamons. How's your different?
As mentioned in the text, it "will shoot off signals to interested user-space applications". It's targeted at "traditional" Linux desktops, like GNOME and everything else I work on.
21 August 2019 at 23:21
Really looking forward to this. I often hit OOM when working with large files in Blender VSE, Inkscape, Scribus or GIMP. Most of the time when these things happen, they happen unpredictably. But if it's interesting, I can try to help with finding reproducible cases - I think partly some of them is OOM related, partly some of them is related to operations blocking the UI thread...
22 August 2019 at 05:40