[BUG] 2.0.1.11/Taalojärvi - Apps crashing, very high memory usage?

Question

12

[BUG] 2.0.1.11/Taalojärvi - Apps crashing, very high memory usage?

asked 2016-05-12 01:23:20 +0300

htmm
703 ●12 ●17 ●17

updated 2016-05-17 10:10:40 +0300

luen

5879 ●73 ●103 ●101

Hi,

Since the Taalojärvi update I have constant problems of apps closing. The browser closes itself every day but I often found the Terminal and the Mail app closed as well. I would use CSipSimple Android App but right after establishing the call the app is crashing. It worked fine in the previous release.

One thing I noticed is te very high memory usage:

[nemo@Jolla ~]$ free
         total       used       free     shared    buffers     cached
Mem: 828692 767020 61672 0 6236 225660

-/+ buffers/cache: 535124 293568
Swap: 627908 73940 553968

Only the Mail app and the Terminal is running. Can we expect a quick fix please? With this my Jolla's functionality became limited. Thanks.

edit retag flag offensive close delete

Comments

have you check btrfs balancing? maybe too little space! lot of thread on tjc about btrfs with instruction.

alloj ( 2016-05-12 13:44:25 +0300 )edit

also didnt last update patch issur with android apps being now able to read sdcard again? maybe had unforesen cosequence? just a thought.

alloj ( 2016-05-12 13:46:59 +0300 )edit

I don't think so. I have enough free space. In the previous version as a workaround I bind mounted the sdcard to the Android file space so I don't think that could be the issue.

htmm ( 2016-05-14 23:51:40 +0300 )edit

have you check btrfs balancing? maybe too little space! lot of thread on tjc about btrfs with instruction.
alloj ( 2016-05-12 13:44:25 +0300 )edit
also didnt last update patch issur with android apps being now able to read sdcard again? maybe had unforesen cosequence? just a thought.
alloj ( 2016-05-12 13:46:59 +0300 )edit
I don't think so. I have enough free space. In the previous version as a workaround I bind mounted the sdcard to the Android file space so I don't think that could be the issue.
htmm ( 2016-05-14 23:51:40 +0300 )edit

Answer 1

2

answered 2016-05-14 18:17:41 +0300

MikeHG
726 ●11 ●15 ●23

Hi,

You can check whether the oom-killer is kicking in using 'dmesg' in the terminal app, immediately after something is killed.

I noticed something very similar recently, though I'm not absolutely sure it was the upgrade to the new version (I've recently installed some new applications / daemons too).

I've found adjusting the zram ratio seems to have helped, although I think there may be side effects too, so don't go crazy. 30% seems to be working fairly well at the moment for me.

https://together.jolla.com/question/96610/more-swap-space/

edit flag offensive delete publish link

Comments

Hi,

No signs of the OOM killer. I also increased the zram ratio to 30 but the behaviour is still the same. I have the feeling these two probelms (closing applications and broken Android support) are not connected.

htmm.

htmm ( 2016-05-14 23:59:40 +0300 )edit

Answer 2

0

answered 2016-05-16 23:14:04 +0300

luen

5879 ●73 ●103 ●101

updated 2016-05-17 02:40:34 +0300

Use top to check if "system_server" is taking up a lot of RAM. I had a similar problem on my Jolla Tablet (web browser crashing when loading a normal website that usually works fine) and found that the process "system_server" took most of the available memory. Despite the name, that process actually belongs to the Android support, so try stopping the Android support or reboot the device.

See also this question: system_server eating up all memory

edit flag offensive delete publish link

[BUG] 2.0.1.11/Taalojärvi - Apps crashing, very high memory usage?

Comments

2 Answers

Comments

Question tools

Stats

Related questions

[BUG] 2.0.1.11/Taalojärvi - Apps crashing, very high memory usage?

Comments

2 Answers

Comments

Question tools

Public thread

Stats

Related questions