Do inactive desktops consume RAM? Specifically concerning widgets on those desktops… But also in general.
Do inactive desktops consume RAM? Specifically concerning widgets on those desktops… But also in general.
]]>
« V12.2b3 beta (Previous Post)
(Next Post) Page indicator (in desktop And in app drawer) – style line And minimap And only text, after swipe left not show… »
D5 Creation
< ![CDATA[
I would like this clarified also. I’m thinking yes, from my experience. I think the word “inactive” may not apply here.
]]>
< ![CDATA[
And if so, how much overhead is there? If I had 50 empty desktops…
]]>
< ![CDATA[
Not that I’d ever have that many desktops, of course. The motivation for my question is ultimately: if I’d want to implement (tasker) trigger-based “screen” switching, would it make more sense to switch desktops or script layout changes with panel movements and such (Layout Manager or similar)
]]>
< ![CDATA[
Yeah I am working on a setup that would pretty much work like you’re talking about and I was just starting to wonder which of these two options is better myself
]]>
< ![CDATA[
In theory more desktops should not consume ram while not loaded. They do however slow down two things:
1. Widgets have a provider which is not managed by LL, so always active.
2. Searches: The more things you have the more time LL will need to find something. For example LL.getItemById or LL.getDesktopByName etc. The implementation seems to be good enough that this isn’t noticeable though.
]]>
< ![CDATA[
Lukas Morawietz, that’s roughly what I’ve assumed/understood as well. Thanks for the confirmation!
]]>
< ![CDATA[
So, to sum up… Empty desktops are cool… It’s the widgets that kill it.
]]>
< ![CDATA[
Well and if you had 16373728337 items on those desktops too, that night slow things up a bit while it’s loading, but yeah
]]>
< ![CDATA[
You could just do what I do and hibernate the widgets on desktop that you’re not using as long as you’re not using that same widget on another desktop.
]]>