Low level memory killer strange behaviour

Question

9

Low level memory killer strange behaviour

bug
oom

asked 2014-12-22 17:47:15 +0200

zurd
86 ●2 ●3 ●5

Hi, I found out that lowmemorykiller works very strange.

Updating one of my email accounts consistently renders my phone completely unoperative, it stops responding to touchscreen and power button. The only way to make it work is to remove battery or wait for random, but often long time.

After investigating this I found that during email update messageserver5 consumes all memory. Then lowmemorykiller starts to killing everytinhg but messageserver5 - it kills user apps, system apps (includind systemd-cgroups and systemd-udevd), on behalf of kswapd0 and, strangely, greedy messageserver5. This continues until real OOM killer wakes up and kills messageserver5:

Jolla kernel: Out of memory: Kill process 984 (messageserver5) score 536 or sacrifice child

Unfortunately I don't use this email account much, so I can't tell if this started in update 9 or 10.

edit retag flag offensive close delete

Comments

Did you start to update that email account directly after installing 1.1.1.27 or some time later?

simo ( 2014-12-22 18:07:43 +0200 )edit

1

It is not the memorykiller acting strange but messageserver5 if it's consuming all available memory.

tigeli ( 2014-12-22 18:16:21 +0200 )edit

First time I started email update next day after system upgrade.

I didn't say messageserver5 works ok, it defenitely is not. But lowmemorykiller instead of killing the memory-consuming process kills all other processes, making phone completely useless till real OOM fires or phone is rebooted via battery reattach.

zurd ( 2014-12-22 18:30:00 +0200 )edit

1

I suggest removing the mail account from settings and try readding it to see if it fixes the messageserver5. When it comes to the OOMKiller it shouldn't really kill lipstick (the home screen) when it isn't running amok but the process that is running amok. The problem is how to properly detect such process. It is hard for every OOMKiller.

leszek ( 2014-12-22 21:06:09 +0200 )edit

I had messageserver5 running amok after I attempted to send an email with an attachment that was too large. messageserver5 kept trying over and over to send the email and the only way I finally got it to stop was by deleting the account and creating it again, just like leszek suggested. This happened to me a few months ago, so it seems that this has not been fixed yet.

shfit ( 2014-12-23 02:33:04 +0200 )edit

Did you start to update that email account directly after installing 1.1.1.27 or some time later?
simo ( 2014-12-22 18:07:43 +0200 )edit
It is not the memorykiller acting strange but messageserver5 if it's consuming all available memory.
tigeli ( 2014-12-22 18:16:21 +0200 )edit
First time I started email update next day after system upgrade.
I didn't say messageserver5 works ok, it defenitely is not. But lowmemorykiller instead of killing the memory-consuming process kills all other processes, making phone completely useless till real OOM fires or phone is rebooted via battery reattach.
zurd ( 2014-12-22 18:30:00 +0200 )edit
I suggest removing the mail account from settings and try readding it to see if it fixes the messageserver5. When it comes to the OOMKiller it shouldn't really kill lipstick (the home screen) when it isn't running amok but the process that is running amok. The problem is how to properly detect such process. It is hard for every OOMKiller.
leszek ( 2014-12-22 21:06:09 +0200 )edit
I had messageserver5 running amok after I attempted to send an email with an attachment that was too large. messageserver5 kept trying over and over to send the email and the only way I finally got it to stop was by deleting the account and creating it again, just like leszek suggested. This happened to me a few months ago, so it seems that this has not been fixed yet.
shfit ( 2014-12-23 02:33:04 +0200 )edit

Answer 1

0

answered 2016-06-23 16:20:50 +0200

nix

301 ●8 ●15 ●20

updated 2016-06-23 16:24:32 +0200

I have similar problem and it started today

top - 16:19:56 up 21 min,  2 users,  load average: 4.06, 3.14, 2.62
Tasks: 236 total,   2 running, 234 sleeping,   0 stopped,   0 zombie
Cpu(s): 60.5%us, 34.1%sy,  0.0%ni,  3.7%id,  1.7%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:    825660k total,   801900k used,    23760k free,       56k buffers
Swap:   627508k total,   458408k used,   169100k free,    42308k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
3163 nemo      20   0 1127m 571m 3768 R 123.4 70.8   9:36.12 messageserver5
   50 root      20   0     0    0    0 D  1.7  0.0   0:28.84 kswapd0
  110 root      20   0     0    0    0 S  0.8  0.0   0:24.41 mmcqd/0
  949 nemo      20   0 48628 2116 1752 S  0.5  0.3   0:01.45 harbour-systemm

I have deleted all mail accounts but nothing changed. Any idea?

edit flag offensive delete publish link

Low level memory killer strange behaviour

Comments

1 Answer

Question tools

Stats

Related questions

Low level memory killer strange behaviour

Comments

1 Answer

Question tools

Public thread

Stats

Related questions