system_server eating up all memory

asked 2014-06-14 14:29:37 +0200

jkario gravatar image

updated 2015-03-27 17:24:28 +0200

Manankanchu gravatar image

This morning my Jolla was totally unresponsive. I managed to SSH into the device but the shell was painfully slow. Did some digging and found out that system_server was eating up most the memory + swap and I think the system was basically thrashing. Has anyone else seen this?

EDIT March 27 2015 by manankanchu: same issue frequently happening on version 1.1.2.16

Tasks: 284 total,   2 running, 282 sleeping,   0 stopped,   0 zombie
Cpu(s):  1.0%us, 15.2%sy,  0.0%ni,  0.1%id, 82.8%wa,  0.0%hi,  1.0%si,  0.0%st
Mem:    830728k total,   822288k used,     8440k free,       68k buffers
Swap:   520180k total,   403924k used,   116256k free,    80016k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 1326 system    20   0 1430m 405m 404m S  0.5 50.0   3:10.84 system_server
 1613 root      20   0 72888  69m  69m S  0.0  8.6   0:00.20 vmtouch
  977 nemo      20   0  350m  59m  58m S  0.3  7.3   2:26.86 lipstick
 1471 nemo      20   0  505m  37m  36m S  1.3  4.6   1:49.43 sailfish-browse
 1365 nemo      20   0  213m  35m  35m S  0.0  4.3   0:19.15 voicecall-ui
 3461 nemo      20   0  279m  32m  31m D  0.4  4.0   0:35.98 jolla-email
 1353 nemo      20   0  159m  14m  14m S  0.0  1.8   0:01.39 maliit-server
11103 nemo      20   0  120m  14m  14m S  0.0  1.7   0:00.92 booster [silica
18158 10016     20   0  846m  11m  11m D  0.1  1.4   0:29.57 ndcloud.android

Tasks: 278 total,   1 running, 277 sleeping,   0 stopped,   0 zombie
Cpu(s):  3.6%us,  8.5%sy,  0.0%ni, 65.8%id, 21.8%wa,  0.0%hi,  0.3%si,  0.0%st
Mem:    830728k total,   821972k used,     8756k free,       68k buffers
Swap:   520180k total,   400132k used,   120048k free,    74004k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
  111 root      20   0     0    0    0 D  4.5  0.0   6:18.87 mmcqd/0
21016 root      20   0     0    0    0 S  3.4  0.0   0:46.25 btrfs-endio-2
21486 nemo      20   0  2604 1012  672 R  3.4  0.1   0:00.09 top
 1471 nemo      20   0  505m  43m  37m S  2.3  5.4   1:42.94 sailfish-browse
   48 root      20   0     0    0    0 D  1.1  0.0   5:52.65 kswapd0
  960 nemo      20   0 98.1m  10m  10m D  1.1  1.3   0:41.75 messageserver5
 1326 system    20   0 1430m 404m 404m S  1.1 49.9   3:08.86 system_server
 1438 10007     20   0  842m 8496 7640 D  1.1  1.0   0:45.17 ndroid.systemui
    1 root      20   0  4964 1072 1072 S  0.0  0.1   0:03.73 systemd
    2 root      -2   0     0    0    0 S  0.0  0.0   0:02.74 kthreadd
    3 root      20   0     0    0    0 S  0.0  0.0   0:00.26 ksoftirqd/0
    6 root      RT   0     0    0    0 S  0.0  0.0   0:03.91 migration/0
edit retag flag offensive close delete

Comments

I also ran into this in 1.0.0.7.16 After unlocking the phone, the UI froze. I tried to switch the screen on and off again using the powerbutton, this caused the red led to blink rapidly. I could only make the phone work again after sshin into devel-su mode and killing system_server.

Interestingly, the journalctl logs were full of kernel errors: http://paste.opensuse.org/21413883

schmittlauch ( 2014-06-28 12:46:45 +0200 )edit

Just added to article that this issue is now frequently happening on my version 1.1.2.16 so I have to reboot every few days ...

What is system_server good for ??

Manankanchu ( 2015-03-27 17:25:40 +0200 )edit
3

@Manankanchu, see for yourself :)

# rpm -qf $(readlink -f /proc/$(pidof system_server)/exe | tee /dev/stderr)
/opt/alien/system/bin/alien-main
aliendalvik-0.15.7-1.armv7hl

In other words it is part of Alien Dalvik.

Self-Perfection ( 2015-03-27 17:54:44 +0200 )edit

@Self-Perfection - thanks for your info, so obviously Alien-Dalvik needs some reworking ;)

Manankanchu ( 2015-03-28 10:14:09 +0200 )edit