How to disable lowmemorykiller [answered]
I've tried all the suggested methods (upping overcommit_ratio, putting 0,0,0,0... into minfree), cc1plus is still being killed when compiling on device.
We have moved to a new Sailfish OS Forum. Please start new discussions there.
I've tried all the suggested methods (upping overcommit_ratio, putting 0,0,0,0... into minfree), cc1plus is still being killed when compiling on device.
From https://answers.launchpad.net/ubuntu/+question/236764 the answe on how to disable OOM seems to be to set
/sys/module/lowmemorykiller/parameters/adj to 9999
and
/sys/module/lowmemorykiller/parameters/minfree to 1
Thank you so much! Now i can do real multitasking again! :-D Will this be persistent or will i have to re-do this after reboot?
DLQ ( 2016-07-02 19:09:15 +0300 )If you really intendo to compile on-device, try this:
http://stackoverflow.com/questions/12964013/reducing-memory-allocation-gcc-command
thanks but that does nothing, gcc fails at allocating memory, so same end result unless you didn't mean ulimit but what the guy had in mind asking that question and lowering memory usage of already compiled app, but that is irrelevant here
szopin ( 2015-07-14 18:03:22 +0300 )This thread is public, all members of Together.Jolla.Com can read this page.
Asked: 2015-07-14 04:52:12 +0300
Seen: 4,485 times
Last updated: Jul 14 '15
Make 'app-autoclosing-on-OOM' optional [answered]
Low level memory killer strange behaviour
[Discussion] Oom Killer fine tuning (overcommit_ratio value)
[regression] OOM killer too aggressive since update 10? [duplicate]
System-Wide Memory Defragmenter
Music Player gets closed even if a track is played
if the task killer is to stay, can we have browser run multiple instances?
why, just why do you compile on-device?
tortoisedoc ( 2015-07-14 07:24:00 +0300 )Because I can (at least in theory, not atm), with tohkbd hoping this will work just like n900 so will be able to put all the commute time to use
szopin ( 2015-07-14 08:45:56 +0300 )Thanks, but cc1plus still gets killed (it does act weridly with those values, as it didn't kill the browser running in the background, with the previous settings I tried everything running in the background was killed too)
szopin ( 2015-07-14 10:41:58 +0300 )@Nieldk this is proper answer, weird behaviour of not killing browser was the oom not kicking in, just watched htop to see how gcc eats through all swap and remaining ram, will need to increase swap (pls convert to answer)
szopin ( 2015-07-14 19:07:08 +0300 )