Ah, but seriously: I remember now one of my thoughts, which actually kept me from writing the issue: I'm not sure whether I have an issue about memory consumption. I don't even really have an issue about the killing of background apps.
Functionally, what I care about is: I want to switch back and forth between browser and email client. I want to do this repeatedly and step by step write an email while looking up things in the browser. Or vice versa: I want to write a forum post, while I repeatedly refer back to some emails, or maybe an attachment there.
I am sure that with the current installation, this workflow doesn't work out of the box, because the background apps are killed, which in turn is because I'm running out of memory.
I could imagine that a waste of memory is at fault. That might be the OS, or any of my open apps.
Or it could be that we are doing the best with the memory, but there just ain't enough memory. And actually the apps should do a better job of saving their state (which email draft were you working on, what is the scroll position that you where at, where was the cursor positioned, what was the qml page stack underneath you). But maybe the toolkit needs to actually support such "rich state saving". And maybe the OS needs to do a better job at restarting apps faster and having a higher resolution screenshot stored such that the time-to-restart is covered a little better.
Or it could be that we simply don't want to bother supporting devices with less than X memory, so it's a wontfix.
So, there we go, practical question: Do I raise the functional issue "Bad user experience switching between browser and email client", or do I raise the technical issue: "No fluent multitasking due to high memory consumption" ?