We have moved to a new Sailfish OS Forum. Please start new discussions there.

multitasking has lags and jitter in update

asked 2015-02-23 14:41:02 +0300

SubtleMind gravatar image

updated 2015-02-23 16:15:30 +0300

chemist gravatar image

While multi tasking lags and jitter are experienced.Some times apps are crashing.

edit retag flag offensive close delete


Agreed. Jitter is much more evident vs previous os update. Oom does seem a bit more aggressive. I can have opera terminated just by browsing with 4 or 5 tabs (no other apps running) - depending in websites complexity of course. but in the past it would never happen.

droll ( 2015-02-23 17:05:39 +0300 )edit

@droll That would mean that Opera itself would use ~400MB of memory, with it would have been killed even earlier.

tigeli ( 2015-02-23 19:17:28 +0300 )edit

really? i actually found the reverse. maybe I am barking up the wrong tree?

droll ( 2015-02-23 20:31:01 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2015-02-23 16:10:30 +0300

tigeli gravatar image

Most of the lag is due device is middle of swapping something in/out from the swap-device and we are working on reducing memory footprint for the applications. However the issue will be the same when your device needs to swap something.

Are you sure that the apps are crashing and not just being killed by the low memory killer? (Are the "crashing apps" always the minimized ones?)

edit flag offensive delete publish link more



@tigeli Will optimisation work currently being undertaken to mitigate the low performance SoC and 1GB of RAM have any negative impact on performance and device behaviour on future phones with more RAM and a more powerful SoC?

boip ( 2015-02-23 18:03:04 +0300 )edit

@boip No, any optimisation we do should have positive impact. :)

tigeli ( 2015-02-23 19:18:20 +0300 )edit

Are you sure that the apps are crashing and not just being killed by the low memory killer? Wow... This is starting to worry me. Talking about the app killing in this tone sounds like you're accepting this as something normal.

Please realise that this is a major issue. Jolla now has the worst multitasking of any OS, due to its unreliability. Instead of killing apps, it would be better to keep them in sleep mode, so at least we don't have to go back in to the app drawer to reopen killed apps.

I was hoping that 1.1.2 would have fixed the OOM problem, but it seems it's still there. Are there no changes to the OOM killing algorithm in the update? Does it still pay to do this? And how can I do this as a non technical user?

bilgy_no1 ( 2015-02-24 08:28:50 +0300 )edit

@bilgy_no1 You know, Jolla-device has never been able to run _unlimited_ amounts of applications at the same time, there has always been a limit when the OOM-killer would kill the apps. Then again OOM-killer and lowmemorykiller are two different things, the first mentioned will kill processes when the system runs out of memory and the latter will kill processes before the system gets hit by OOM-killer (for example because you don't want to make the system unresponsive for x amounts of seconds). Also there is a thing called memnotify which is able to notify processes to lower their memory pressure running garbage collectors and such..

With 1.1.2 the lowmemorykiller have been fixed to take the available swap properly in account, so the experience is a _lot_ better than with 1.1.1.

tigeli ( 2015-02-24 08:57:50 +0300 )edit

Thanks for the clarification. I'm waiting for the public release of 1.1.2, so hope to experience the improvements soon...

As for unlimited apps open, I think it would be better to put apps in sleep mode than to totally kill them. That way, they are at least still available on the home screen. Of course, only do this in kow memory state instead of killing which happens now. So if there's no memory problem, leave them running (full multitasking).

bilgy_no1 ( 2015-02-26 08:58:11 +0300 )edit
Login/Signup to Answer

Question tools

1 follower


Asked: 2015-02-23 14:41:02 +0300

Seen: 272 times

Last updated: Feb 23 '15