Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Complaints Mounting About iOS 13.2 Being 'More Aggressive at Killing Background Apps and Tasks'
- Thread starter MacRumors
- Start date
- Sort by reaction score
Thanks for the link.
[automerge]1572955096[/automerge]
The post from eskimo suggests that the major background task changes happened in an early iOS 13 beta, which doesn't line up with the wisdom of the crowd that this problem started with iOS 13.2 - but perhaps more people are reporting it now because it's more widely known to be a problem.
The post indicates that there was a major change to the amount of time a background task could exist before being suspended:
... but it's not clear that those 'suspended' tasks will lose all state and context, as appears to be the case now.
My understanding of 'suspension' would be that the state and context should be preserved in order to be restored at a later time, but the current behaviour appears to simply kill the app entirely, necessitating a full reload when switching the task back. This is certainly not described by eskimo's post, and I can only conclude that this is indeed an unintended flaw.
Last edited:
I had none of these issues with 13.1.1 and I was an iPad Pro multi-tasking heavy user. I updated the day each of the point releases were released for iOS 13. I can only conclude that something changed in 13.2.
I'm not saying that throwing more RAM at a problem is a good thing. I'm just saying for all these people who want Apple to throw more RAM in: If it doesn't need more RAM, all that RAM is going to do is eat through your battery faster.
I'm not saying that throwing more RAM at a problem is a good thing. I'm just saying for all these people who want Apple to throw more RAM in: If it doesn't need more RAM, all that RAM is going to do is eat through your battery faster.
Experiencing the same problem with my 11 Pro, quit youtube for couple of minutes and when I opened it again it refreshed/started as new. So damn annoying. I hope they fix this.
I would say that Safari is restoring state incompletely. If a web page with forms doesn’t have scripting, then it would be trivial to repopulate the fields in the form. Pages with JavaScript wouldn’t be quite as easy. I rarely see web pages these days without JavaScript.
A point that many people were missing is that if something is implemented in a way they don’t like, it doesn’t necessarily mean it’s an accident or bug. In software development, many shops will close a bug report as WAD (Works As Designed). If many people complain, they’ll change the design.
I sincerely don’t know exactly what is objectionable to you. Is it that I asked people to read a post I wrote that I thought would answer their question? Do you feel I should have copied and pasted the entire answer? Do you think I should have given a unique answer to each phrasing of the same question? Is the word “Please” offensive to you? Are you objecting to the way “Please read post #380” is repeated several times in one post? Note that it says “- - Post merged: Friday at 9:50 AM - -“. MacRumors did that, not me. When I saw several people asking the same question, I wondered “Why don’t they just ‘Like’ the first posted question instead of rephrasing it?” It felt a little harassing. In hindsight, I believe that wasn’t the intent. People most likely just read my first post and replied without first reading any posts that followed. If you look at all the replies to my post, do you honestly feel that no one was being snarky?
That’s all I’m going to say on this thread. (I can hear the clapping.)
I’ve read conflicting reports. I read one report where locking the phone for a short amount of time causes killing of background applications.
I have done the locking and still no memory management refresh issues in my case. Most of what I am reading is positive results. The number not working seems small so far.
[automerge]1573001632[/automerge]
So far on my iPad Pro 13.3 fixes this issue as well as a couple other bugs we reported during testing to apple
Yes, changes can be by design. If this change is by design, that’s highly objectionable indeed because it was introduced in a minor release, not adequately documented, and confusing in behavior both to developers and users. (There don’t even appear to be good diagnostics to developers that an app was killed for new policy reasons.)
So Apple is either being highly objectionable, or it’s a bug.
If it’s a bug, it’s problematic that this is the third minor 13.x release (already on poor reputation) and yet they still make changes significant enough to cause such issues. Whatever change caused this clearly shouldn’t have been merged into 13.x. Beyond that, once it became clear in the beta cycle that there was a problem, they should have reverted. Maybe they thought they had fixed it. Probably, though, they really wanted Deep Fusion and AirPods Pro Support out the door. Pressure to ship happens. It’s not great.
As for what’s objectionable about your posts, I don’t know what to tell you if you can’t see it. Try interacting with people a different way.
i don't think this was a RAM management issue. I think the Mail app was causing everything to crash. I was having this issue persistently. Last night decided to stop using the mail app for whatever reason because gmail app is a lot smoother and ever since getting rid of the mail app, safari and open apps haven't crashed.
Just tried this and it doesn’t work for me; all the other apps still close down. YouTube/Amazon to name but two lose the last page I was on and in less than 30 seconds of going back they revert to the Home screens.
I´ve now installed the beta 13.3, and now my iPad works as expected again, with no more force closing of apps!
I was speaking more from experience of using 3rd party code, written in Swift, in my ObjC projects.
The "Charts" library, which was originally written in Java for Android, was a bit of a nightmare with each update of Swift. A few times I attempted to try and fix the changes myself just to get my project compiling again but it was more work than I had time for.
It was enough to put me off considering Swift for my own coding.
Just found out that not only does iOS forget to keep YouTube in memory but if I start a video then whilst remaining inside the App I stop said video, press close on the video then immediately go back to it, the YouTube App forgets where I was last watching it from.... It plays the video from the beginning.... Do it again and again and not once does it remember where I last watched it from.
THIS IS NOW BEYOND ANNOYING!!!
THIS IS NOW BEYOND ANNOYING!!!
Seems like things were behaving that way whether or not the Mail app was being used. And it's not that things crashed, more like just had to be loaded pretty much each time as if they were just launched.
Using an iPhone 6S on iOS 13.2. I am still getting various kinds of bugs, even using Apple own apps (eg Phone app, Mail app, Files app, App store, iTunes & iCloud account,) that have to restart the phone. Even killing the app doesn't seem to work. This is the worst iOS version I have used since 2010.
It is abundently clear for some time now that Apple's emphasis has shifted and as a result they really need to spend more resources and dedicate time on their software projects (eg maybe pay for more full time in-house staff that don't get shifted around).
It is abundently clear for some time now that Apple's emphasis has shifted and as a result they really need to spend more resources and dedicate time on their software projects (eg maybe pay for more full time in-house staff that don't get shifted around).
That makes sense. Fixing third party stuff is awful. My project didn't have very many dependencies, so I wasn't thinking about that.