XPost: comp.sys.mac.advocacy, misc.phone.mobile.iphone   
   From: YourName@YourISP.com   
      
   On 2023-10-01 22:05:14 +0000, candycanearter07 said:   
   > On 10/1/23 16:59, Alan Browne wrote:   
   >> On 2023-10-01 17:43, candycanearter07 wrote:   
   >>> On 10/1/23 16:36, Alan Browne wrote:   
   >>>> On 2023-10-01 16:38, sms wrote:   
   >>>>> On 10/1/2023 12:20 PM, Patrick wrote:   
   >>>>>   
   >>>>>    
   >>>>>   
   >>>>>> Damn Instagram.   
   >>>>>>   
   >>>>>> Why is it always the app that nobody uses that makes the iPhone   
   overheat.   
   >>>>>   
   >>>>> LOL, here are the iOS apps that are downloaded the most:   
   >>>>> 1. TikTok   
   >>>>> 2. Instagram   
   >>>>> 3. Facebook   
   >>>>> 4. WhatsApp   
   >>>>> 5. Telegram   
   >>>>>   
   >>>>> I did see a complaint that Instagram causes Android phones to heat up   
   >>>>> as well. It seems like Instagram will just use as much CPU power as it   
   >>>>> can get. This is not really a bug in Instagram, the operating system   
   >>>>> should be limiting the amount of resources that an app can consume.   
   >>>>   
   >>>> Not at all.  The OS cannot tell if badly written software is doing   
   >>>> something useless driving up power consumption.   
   >>>   
   >>> The operating system controls thread scheduling and memory. They can   
   >>> just lower the apps priority if its past a certain usage percentage, or   
   >>> outright kill it.   
   >>   
   >> Some apps justifiably need a lot of CPU so the OS cannot do more that   
   >> allow the app / thread to run its time slice until the slice is over or   
   >> pre-empted by something with higher priority for which no other core is   
   >> available.   
   >>   
   >> Could one design an OS that applies the rule as you say?  Sure.  But   
   >> that is not the case in general purpose OS'.   
   >>   
   >> Could the OS detect race conditions and kill a thread (or several)?   
   >> Probably.  My example has no such possible state.   
   >>   
   >> And while my example might be trivial, there are cases where converging   
   >> on a solution with many variables can take a hell of a lot of CPU and   
   >> time.  And it's a very valid thing for a program to do.   
   >>   
   >> The main point is that OS' don't arbitrarily kill processes (or   
   >> throttle them) just because a given process is using a lot of CPU.   
   >   
   > At the very least, it should warn the user if a program is using a lot.   
      
   At the very least the user should have enough brains not to use utter   
   crap "Social Media" apps like Instagram.  :-p   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)