5,605,373 Members 41,134 Now Online
XDA Developers Android and Mobile Development Forum

Issue with stock Music Player using available RAM!

Tip us?
 
VHAHONGRANTC
Old
#1  
Junior Member - OP
Thanks Meter 1
Posts: 18
Join Date: Sep 2008
Location: Kaneohe
Exclamation Issue with stock Music Player using available RAM!

Hey Folks,

I have an issue with the built-in stock Music player constantly taking all of the available RAM, which causes Android to start killing other processes like the launcher (Apex Pro), Tasker, nearby devices service (force closes occasionally), etc. It is very odd. I have tried several attempts to remedy the situation. I have, so far, cleared the Media Storage data, cleared the Cache partition from the boot recovery menu, have music on built-in storage and un-mounting my MicroSD card, to which none of these efforts helped. It seems like the Music Player app has a memory leak, which I am wondering if this was introduced in 4.3. I did not see it listed yet in the 4.3 issue threads, and not really sure if 4.3 is the culprit. I upgraded to the S4 from an S2 recently and a week later the official 4.3 upgrade was available. Thus, I do not know if this issue was happening in 4.2.2.

The interesting thing is that this leak or loop is occurring whether or not I have music on the device. So, to be clear, the issue specifically is when I launch the Music Player and then go to Task Manager to see the used RAM, the RAM will just continue to get used up until it reaches about 1.70GB or so out of 1.78GB available and then Android will start killing other processes to accommodate for more memory. This is when Apex and /or Tasker and other services start getting the ax. What's more, if I kill the Music Player (either right away or later), the memory continues to be consumed until it reaches about 1.5GB - 1.6GB and then finally releases and drops to 700MB - 900MB.

I am on a stock ROM, non-rooted and I have also confirmed this issue with my wife's S4 as well. We can use Google Play Music with no issues, but prefer the stock player if there is a solution to this "memory leak" or other situation that is causing the issue. If anyone has some insights as to what this issue is and a fix, please let me know. Also, if anyone can launch the Music Player and watch the RAM in Task Manager to confirm that this is or is not occurring on other S4s out there as perhaps it is an issue that some may not have noticed. In fact, my wife has been using her device in the car for a couple of weeks and streaming with Bluetooth and not noticed this was occurring. However, if she were to have music and use Maps/Navigation at the same time with this issue, Maps will get killed along with other multitasking tasks. I happened to noticed this behavior when I moved my music on the device and was playing around with the player, when I saw that Tasker restarted itself and then shortly after the nearby devices service forced closed and the music app got real sluggish. I then started observing the RAM usage with the launch of the player and realized why apps were closing. The funny part is that the music plays fine and never dies, it just kills everything else in its wake.

Any insight to this will be greatly appreciated. Also, I have been scouring the forums and Google in general to see if this has been mentioned and have not found this exact situation. However, if I did overlook a thread/post that has this as a known issue, please let me know what that link is. Thanks.
 
KCRic
Old
#2  
KCRic's Avatar
Senior Member
Thanks Meter 243
Posts: 1,131
Join Date: Aug 2010
Location: Overland Park
First off, damn. You might want to take a refresher course on how to say what you mean without all the extra words. You wrote a book man. 90% of what you typed is unnecessary. Nobody wants to read all of that and must won't even entertain a response. Just a friendly heads up.

Now, are you sure that the RAM is being taken up by the music app and not a combination of apps/processes? The stock task manager isn't very good for situations like this so you'll need to download a system monitor. There are quite a few out there, take your pick.

Could be that when you open the music player the media scanner is eating up RAM along with other processes. Those together are killing your memory. If that's the case you need to create a .nomedia file to place in the folders on your internal/external memory. Also, do you have any other music or media apps installed?

Figure out those then post back. You might try uninstalling all your apps then reinstall them one by one ( backup first). Yes, it can take a while if you have a lot but once you install the culprit - you'll know it. Hope that helps.
MyTouch 3G (Yeah, I know...) Rooted w/ unlocked bootloader - Retired
G2 (Desire Z) Rooted w/ unlocked bootloader and carrier restriction - Retired
Epic 4G Touch (Galaxy S II) - Retired
Nexus 4 16GB - Rooted w/ unlocked bootloader - Retired
T - Mobile Galaxy S 4 - Knox Free. Running Wicked v10 w/ Chronic kernel - Current

24kbps 1080p w/ 320kbps audio @ 48KHz camera mod by me. Also w/ How-to.
 
VHAHONGRANTC
Old
#3  
Junior Member - OP
Thanks Meter 1
Posts: 18
Join Date: Sep 2008
Location: Kaneohe
Default SOLVED!!



Ah, thanks for the heads up! Sorry about the long-winded post, I just wanted to convey the issue and what I have done so far. In future posts, I will be much more concise and to the point.

On a good note, I have solved my issue and found that if you disable/freeze/uninstall apps but still want to use the built-in music player, there is a conflict if you disable S Voice. I was going through the settings in the music player and noticed the voice control feature (which was unchecked), but clearly the player still wants to talk with or "see" S Voice out there. I took a shot in the dark and once I re-enabled S Voice, the gobbling of RAM from the music player launching stopped. Yay!!
 
VHAHONGRANTC
Old
#4  
Junior Member - OP
Thanks Meter 1
Posts: 18
Join Date: Sep 2008
Location: Kaneohe
Default Not solved!



Well that victory was short lived. That seemed to have only worked for about 10 minutes and it is back to the same memory gobbling issue when the player is launched. I reactivated Google Play Music and am using that with no issues, so it seems that will have to do.
 
KCRic
Old
#5  
KCRic's Avatar
Senior Member
Thanks Meter 243
Posts: 1,131
Join Date: Aug 2010
Location: Overland Park
Well that was all I had. I don't use the stock music player since I stream with Google Music.

You might look in the app store for an app to replace the stock one. Then uninstall the stock app so you don't have the issue anymore.

Sent from my SGH-M919 using xda app-developers app
MyTouch 3G (Yeah, I know...) Rooted w/ unlocked bootloader - Retired
G2 (Desire Z) Rooted w/ unlocked bootloader and carrier restriction - Retired
Epic 4G Touch (Galaxy S II) - Retired
Nexus 4 16GB - Rooted w/ unlocked bootloader - Retired
T - Mobile Galaxy S 4 - Knox Free. Running Wicked v10 w/ Chronic kernel - Current

24kbps 1080p w/ 320kbps audio @ 48KHz camera mod by me. Also w/ How-to.
Tags
leak, memory, music player
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes