Ask / Submit

Revision history [back]

click to hide/show revision 1
initial version

posted 2016-12-05 01:13:55 +0200

oomk kills too much apps

Hello,

i remark shortly that the oom-killer function of the system stop too much apps.

For example if i take a native browser like the official one or webcat.
And try to load all the iso file from this website: http://iso.linuxquestions.org/

then later, the wlan connection will be unstable, all of of interruption will be done. Then all the active app will crash. The covers still remain in home, but by taping on it, the app will be recall.

Firstly, from this oomk function, i would expect that it kill first the app which take the most place in ram.
Or maybe that it kills after a specific "survival" priority schema.
I can represent my self that a webbrowser would have a low priority. And if it takes too much ram, it could be killed first alone, before other one.
Then, maybe it's a kind of speculation from me, but i can't imagine that something with this function disturbed the wlan connection.
It could be an other bug, but each time i try to load a lots of file, the wlan connection goes interrupted, until all the apps will crash.
It's for me too difficult not to associate it, with the oomk, there is for me a kind of bug behind.

I find actually that the oomk action is a little bit too rough.
Would it be possible to optimize/improve it please?
Maybe analyse what's happened on the wlan at the moment of an high dataloading?

I have a jp1, with last official release.

oomk kills too much apps

Hello,

i remark shortly that the oom-killer function of the system stop too much apps.

For example if i take a native browser like the official one or webcat.
And try to load all the iso file from this website: http://iso.linuxquestions.org/

then later, the wlan connection will be unstable, all of of interruption will be done. Then all the active app will crash. The covers still remain in home, but by taping on it, the app will be recall.

Firstly, from this oomk function, i would expect that it kill first the app which take the most place in ram.
Or maybe that it kills after a specific "survival" priority schema.
I can represent my self that a webbrowser would have a low priority. And if it takes too much ram, it could be killed first alone, before other one.
Then, maybe it's a kind of speculation from me, but i can't imagine that something with this function disturbed the wlan connection.
It could be an other bug, but each time i try to load a lots of file, the wlan connection goes interrupted, until all the apps will crash.
It's for me too difficult not to associate it, with the oomk, there is for me a kind of bug behind.

I find actually that the oomk action is a little bit too rough.
Would it be possible to optimize/improve it please?
Maybe analyse what's happened on the wlan at the moment of an high dataloading?

I have a jp1, with last official release.

note: i remark now that after my experiment with the official browser, that this one could never start again.
After start it, the cover is working on it, and after a while it disappear again without to have the browser-app.

Have a nice sail.