4 ms·

> My main reservation with this setup is that Android's memory management is fatally flawed and processes can be terminated at any time without warning. It's u

> My main reservation with this setup is that Android's memory management is fatally flawed and processes can be terminated at any time without warning. It's unbelievable, Would we allow this behavior on desktop OS? Mobile operating systems seems to have taken the worst features from typical computer and embedded systems. But who dare question the Duopoly. I just had rant about this the other day with reg Google Clock not functioning and people loosing jobs because of it[1]. [1] https://news.ycombinator.com/item?id=28411912 https://news.ycombinator.com/item?id=28411912

Yoric 5y ago
> > My main reservation with this setup is that Android's memory management is fatally flawed and processes can be terminated at any time without warning. > > It's unbelievable, Would we allow this behavior on desktop OS? Mobile operating systems seems to have taken the worst features from typical computer and embedded systems. But who dare question the Duopoly. That... is actually a feature of the Linux Kernel. How else would you handle the exhaustion of physical + swap memory or file descriptors, etc.?
- Abishek_Muthian 5y ago
  I agree, While the overzealous app killing in the name of preserving power i.e. battery is not the fault of Linux kernel alone[1] as I've mentioned in the linked thread in my original comment one of the things we gain by switching to an aftermarket android ROM is predictable app behavior. [1] https://dontkillmyapp.com/ https://dontkillmyapp.com/
- dredmorbius 5y ago
  On full-blown Linux, you've the option of setting priority / status for specific processes. On Android, the reaper is actually the JVM, so far as I understand.
- Dylan16807 5y ago
  Android doesn't wait for an emergency.
  - dredmorbius 5y ago
    Android is the emergency.
- tomjen3 5y ago
  Return null, and let the program handle it in a graceful manner. Like the standard says to do to indicate an error.
- easton 5y ago
  iOS does this too. It works fine. The trick is to not kill the alarm service (which Android shouldn't do either, given that's never the thing chewing up resources).

Yoric 5y ago

> > My main reservation with this setup is that Android's memory management is fatally flawed and processes can be terminated at any time without warning. > > It's unbelievable, Would we allow this behavior on desktop OS? Mobile operating systems seems to have taken the worst features from typical computer and embedded systems. But who dare question the Duopoly. That... is actually a feature of the Linux Kernel. How else would you handle the exhaustion of physical + swap memory or file descriptors, etc.?

Abishek_Muthian 5y ago
I agree, While the overzealous app killing in the name of preserving power i.e. battery is not the fault of Linux kernel alone[1] as I've mentioned in the linked thread in my original comment one of the things we gain by switching to an aftermarket android ROM is predictable app behavior. [1] https://dontkillmyapp.com/ https://dontkillmyapp.com/
dredmorbius 5y ago
On full-blown Linux, you've the option of setting priority / status for specific processes. On Android, the reaper is actually the JVM, so far as I understand.
Dylan16807 5y ago
Android doesn't wait for an emergency.
- dredmorbius 5y ago
  Android is the emergency.
tomjen3 5y ago
Return null, and let the program handle it in a graceful manner. Like the standard says to do to indicate an error.
easton 5y ago
iOS does this too. It works fine. The trick is to not kill the alarm service (which Android shouldn't do either, given that's never the thing chewing up resources).