This app was mentioned in 8 comments, with an average of 2.88 upvotes
There is a setting named "Don't keep activities" in the developer settings. It doesn't kill the process but it causes the activities to lose their states (they save to bundle)
If you want the process to die, use an app that fills up the device memory forcing the lowmemorykiller to kill other background processes
https://play.google.com/store/apps/details?id=me.empirical.android.application.fillmemory
Always good to test your application when it is low on memory :P - Fill-ram
Here is another option that was posted in this sub some time ago: - Android-Developer-Toolbelt
It's simple because they completely ditch any kind of support for persistence across process death.
At least their samples should handle it if the libraries don't. But it doesn't so it kinda sucks, even if it has Rx integration and all that.
Don't trust any navigation library that doesn't remember where you are across <strong>low memory condition</strong>. If their sample shows you how to do it, that's great! If it doesn't, then the navigation lib is at that given state kinda garbage/pointless, a gateway to writing terrible apps.
If you ever checked the permission/result handling or the router transaction backstack in Conductor, this is why it looks so complex. Because Conductor actually does this kind of thing right. It doesn't just throw away your state because "it's too difficult to handle it".
The multitasking seems a bit faster than another cheap tablet I've tried, but I'm skeptical about the 4GB after trying this app:
It starts glitching out and the app eventually crashes when it tries to go above 1GB.
Yeah, Firefox thinks it is incorrect to remove tabs if it doesn't know that you actually want the tabs gone.
The Brave option is called "Close tabs on exit", but I just tested it, and it removes tabs as soon as the app gets purged from memory when using https://play.google.com/store/apps/details?id=me.empirical.android.application.fillmemory to fill up my memory.
I assume your ReduxStore is not "hydrated" and therefore if you test the app against process death (android low memory condition) then it just restarts from zero?
If you can't put the app in background then terminate from AS then launch from launcher, then I use https://play.google.com/store/apps/details?id=me.empirical.android.application.fillmemory&hl=en which works fairly reliably for killing off everything.
I'm not sure. But if you try out <strong>this app</strong> then you'll be able to see what it's like when the launcher gets process death.
Put the app in background then run this app
https://play.google.com/store/apps/details?id=me.empirical.android.application.fillmemory&hl=en
You'll find that it's not just 3rd party app killers that cause this scenario :)