apps get killed / freezed too soon. [duplicate]
i do never run more then 5 to 6 apps in parallel, mostly only 3-4. however today i had open: sailorgramm, mail and browser. i did some browing: during this sailorgramm got killed. i noticed after five minutes, that when i clicked on sailorgramm the app was restarted. while sailorgramm is not running you will not receive notifications on new messages. this did happen. yesterday i was listening to music, while browsing music player did stop. this happened twice. i never have more then 2 tabs 'open', mostly only one.
i am not sure what the correct fix is: but a running player should not be freezed. and while running apps are required to receive notifications, messengers should not get freezed too.
duplicate of: https://together.jolla.com/question/108599/11928-alarming-oom-behavior-killing-apps/
I'm sure you can find a duplicate: https://together.jolla.com/questions/scope:all/sort:activity-desc/page:1/query:oom/
Tanghus ( 2015-09-30 01:17:57 +0300 )editis this a normal behavior since the last update? I mean i see my opened apps as covers in the home screen but the seem to be frozen, blury and the quick action buttons are gone. when I tap on the cover, it restarts!?
Dragomir ( 2015-09-30 09:33:21 +0300 )edit@Dragomir Yes, this is normal now. Apps not closed via swipe down or the home screen (but e.g. by the OOM Killer or because the app crashed) will leave a "ghost" cover. When touched, the app will be restarted.
t-lo ( 2015-09-30 09:42:48 +0300 )edit@ Dragomir: yes that is the new normal. Auto-killed applications stay visible in frozen state and serve as quick launch icons rather than representing miniature screens of actually running programs.
Somebody mentioned before: WebOS tells the user: there are too many "cards" opened, please close some ... before opening new... This was a polite way to prevent pushing the system into swapping / slow down by opening more processes.
Sailfish' approach is very rude and brute force in comparison.
My impression is that there is some kind of preference installed on what to kill first: for example I found the Sailfish media player to be less easy killed than a 3rd party one like QuasarMX but still... it is very rough behavior.
Music streams or authenticated browser sessions should not be killed just like that.
Looks like heavy work in progress and I find the experience now worse than in early days.
Sure the UI interface is fast, but when it is time to get things done, I experience more hickups and killed programs than ever since early 2014. Anybody can agree with this?
vandersmash ( 2015-09-30 09:46:43 +0300 )edit@Tanghus: yes if i knew i have to search for oom, i just now ooomph.
https://together.jolla.com/question/108599/11928-alarming-oom-behavior-killing-apps/
pawel ( 2015-09-30 12:44:08 +0300 )edit