Too many "open" programs

[mhc48]

Often when I press the "back" arrow at the bottom of my phone I will see 10 -12 open but (I presume suspended programs). Suspended or not, I believe they must be using RAM because that is when I get the message about "Resuming". Then I have to laboriously close each open program(I say laboriously because I often miss the tiny X and open the program instead). So far the main thing I actively dislike in Win 10 Mobile that I haven't seen any hint of being changed.

Each program should have an X at the top right corner to close it while you are in the program. Or if Win 10 is to be "universal" should be able to be closed by swiping down from the top of the phone screen. That I know would displace the ability to view the notifications screen, but to me, all those "open" programs is even more of a concern.

 

[ajcollins09]

You can also close apps in the multitasking menu by swiping down on the app.

 

[mhc48]

You can also close apps in the multitasking menu by swiping down on the app.

Ah yes, that's true, thanks. But my real concern is having 10-12 "Windows" open

 

[Asskickulater]

Ah yes, that's true, thanks. But my real concern is having 10-12 "Windows" open

You are correct, suspended programs do in fact eat up ram, though I'm not sure what the issue is? Yea, if you open to many apps you will run out, I don't see what your getting at with this? It's not an issue, its simply you hitting your hardware limitation.

 

[Dewg]

RAM is just a big pool of space for programs to use. It doesn't matter if you're using 10% or 90%, it's the same performance. Windows will handle the pool on its own, closing apps to free space as needed when new apps launch.

 

[mhc48]

I have to disagree with both of you.

Dewg, I routinely find 10 -12 apps/programs open in the background on my phone, so Windows 10 doesn't seem to be doing a very good job of closing apps on its own when new ones launch.

The problem, Asskickulator is that I don't realize or get any notice of the number of open background apps until a new one I try to open hangs or one I try to go back to gives me the "Resuming" message. However, as soon as I close those 10 "open" background apps, the phone speeds up, apps open quickly etc. This was a problem in past versions of Windows too and MS solved it by allowing you to close an un-needed app when done using it either by touching the X on the corner or swiping down from the top as I've always done on my Surface Pro 3 under 8.1 and as you can still do in Win 10 on the Surface and even my Dell Venue 8 Pro. But not Win 10 Mobile.

In my opinion the ability to close an app from within the app is even more needed in Win 10 Mobile where devices typically have less RAM.

 

[Asskickulater]

I have to disagree with both of you.

Dewg, I routinely find 10 -12 apps/programs open in the background on my phone, so Windows 10 doesn't seem to be doing a very good job of closing apps on its own when new ones launch.

The problem, Asskickulator is that I don't realize or get any notice of the number of open background apps until a new one I try to open hangs or one I try to go back to gives me the "Resuming" message. However, as soon as I close those 10 "open" background apps, the phone speeds up, apps open quickly etc. This was a problem in past versions of Windows too and MS solved it by allowing you to close an un-needed app when done using it either by touching the X on the corner or swiping down from the top as I've always done on my Surface Pro 3 under 8.1 and as you can still do in Win 10 on the Surface and even my Dell Venue 8 Pro. But not Win 10 Mobile.

In my opinion the ability to close an app from within the app is even more needed in Win 10 Mobile where devices typically have less RAM.

That could very well be a bug, but that is the exact kind of bug you should be expecting, though I've run atleast 20 apps without any issue like that, are you using a 512 mb device?

Also... whats wrong with holding the backspace to close an app... surely you cant be that busy.

 

[mhc48]

I'm running the latest build on both a 930 and a 635. The problem is more pronounced on the 635, but happens on the 930 as well when there are 12 or so apps open.

As far as what is wrong with that, unless I'm missing something that you know, Asskickulator (certainly possible), clicking the back arrow ( what I think you are calling the backspace) only array of pictures of all the apps you have open on your phone in their last open status. In order to close each one, you have to cycle through them and either click the X on each or swipe down on each until they're all closed (or until you've closed as many as you want to). On a phone I'd far prefer to close each app when I'm done using it.

 

[Asskickulater]

I'm running the latest build on both a 930 and a 635. The problem is more pronounced on the 635, but happens on the 930 as well when there are 12 or so apps open.

As far as what is wrong with that, unless I'm missing something that you know, Asskickulator (certainly possible), clicking the back arrow ( what I think you are calling the backspace) only array of pictures of all the apps you have open on your phone in their last open status. In order to close each one, you have to cycle through them and either click the X on each or swipe down on each until they're all closed (or until you've closed as many as you want to). On a phone I'd far prefer to close each app when I'm done using it.

sorry, typed that out on my phone and it auto corrected back button to backspace and I didn't notice it.

and well, its not necessary to close apps though, w10 probably has a bug that your experiencing, windows usually manages memory well, I think the 930 has the same amount of ram as the 1520 (my phone) doesn't it? Though looking at posts in general, it seems like 1520 is the most stable device for windows 10, so maybe that's why I don't have the issue. The point of my rambling is that the OS is supposed to handle memory so that what your talking about doesn't happen. The only reason the ability to kill apps exists is mostly for when an app crashes requiring the app to be reloaded (well.. and people obsessively asking for it)