[1.1.9.28] Alarming OOM behavior (killing apps)

asked 2015-09-10 23:30:59 +0300

nodevel gravatar image

It seems that the memory management got really bad in SailfishOS 1.1.9.28.

I have just 4 native apps open (no browser, just Calendar, Settings, etc.) one of which is the LLs Video Player with a paused video. Memory management repeatedly kills the video player with the paused video and I am repeatedly losing the progress.

What is worse, with the new behavior - cover staying even when the app gets killed - I never know which apps are running, so I notice that the video player got killed only when I attempt to resume the video.

I know that we had similar situation when the 10th update came out, but this is way worse than that. If I remember correctly, the sailors at Jolla optimized the system quite soon and everything was resolved in the 11th update. Could this please be fixed/optimized before the final Sailfish OS 1.1.9 comes out?

edit retag flag offensive close delete

Comments

8

Could I get the output.txt-file from command "devel-su journalctl -b >output.txt", you can send it to tigeli@jolla.com and I will check what's happening.

tigeli ( 2015-09-10 23:38:29 +0300 )edit
3

@tigeli Will do! Thanks for the swift response.

EDIT: Now sent.

nodevel ( 2015-09-10 23:45:26 +0300 )edit

I suspect maybe a gstreamer 1.x problem. I had it also once. It seems like eating a lot of memory.

leszek ( 2015-09-11 00:14:37 +0300 )edit
1

I also suffer from this, but I don't have VideoPlayer opened. For me it seems to be related to tracker-store which eats memory and CPU. Survived even reboot. Phone is being unusable for 2 hours now, as every App closes right after start.

thomas.goertz ( 2015-09-11 08:24:26 +0300 )edit
3

I am also hit by this. When using some Android app that consumes a lot of memory it kills even running media players that play music while on the go. I was using flow player and later tried QuasarMX to play some music that suddenly stopped when trying to calculate a route in automapa(android tbt navigation). I went back to the player just to see it got killed... This definitely needs fixing. I am perfectly happy with OOM management killing apps and losing progress if an app is badly behaved or unprepared but OOM should chose the apps that are about to be killed much more diligent than it is now.

Shoppinguin ( 2015-09-11 09:48:58 +0300 )edit