Memory Issues

[bhatech]

I have YouTube app suddenly misbehaving from today evening. Keeps force closing, eventually works and then again closes after some time. Restart doesn't help as well. There were updates to both YouTube and Google app, probably something screwed up. The constant location icon bug after the latest Google update also sucks.

Edit: YouTube issue was probably because I was on the beta program. Left beta and reinstalled app, works fine now. Got to unenroll from all these beta program sign ups from apps

 

[ClintRo]

I'm not noticing it either but it could be a photo that you've forgotten about.

Lol.... That is what I was implying.

 

[chezm]

The issue hasn't returned, I'm chosing all camera scenarios for front facing and it won't lock up or freeze. Very happy because I started to worry it was hardware related.

Update: ok no the problem still exists, only when trying to use portiat mode front facing. Can anyone confirm they aren't experiencing this as well? Reboot fixes it not sure if memory related.

The only memory issue impacting me is related to front facing camera freezing causing camera app to crash, reboot fixes it. I've played Apple music and used navigation no issues, apps haven't crashed that way for me yet

 

[alodar101]

Well I had the picture/music memory issue today. I was listening to a podcast in my car (Pocket Caster), driving through the neighborhood. I saw a tree that was a brilliant yellow so I stopped to take a picture, and on the second one, zap, Hardcore History (the podcast) was shut down -- the app closed.

i would have just turned the podcast back on... And moved on. Is this really a big deal.? I am sure there are memory combinations and app combinations that will cause someone to lose thousands of dollars, or, heaven forbid, someone to lose their life. Though i would argue..." Why are you using a phone app to do this". But to the common user, trying to play music and watch a video while taking a pic and using my BT head set and navigating Waze on Android auto and an app closed so I'm pissed... Doesn't do it. Want to prove it to the common user, first caLm down and get off your soapbox. Then be very clear about what you're doing, what apps you're running, what versions you're running. What order you do then in. Tell the common user what happens, and what you expect. Tell us if anything you're using is beta or canary. Then us non-genius common users can try it. And if it happens to us.. we will elect you president. Until then, only a few of you have an issue, and a whole bunch of people think this might have happened to them on Tuesday.., but they're not sure.

I'm sorry. I've read all the posts.. on many of the forums. I've tried to follow the issues and test it on my device. I can't. So... Think like a tester and provide a repro, with serious repro steps.

 

[Almeuit]

i would have just turned the podcast back on... And moved on. Is this really a big deal.? I am sure there are memory combinations and app combinations that will cause someone to lose thousands of dollars, or, heaven forbid, someone to lose their life. Though i would argue..." Why are you using a phone app to do this". But to the common user, trying to play music and watch a video while taking a pic and using my BT head set and navigating Waze on Android auto and an app closed so I'm pissed... Doesn't do it. Want to prove it to the common user, first caLm down and get off your soapbox. Then be very clear about what you're doing, what apps you're running, what versions you're running. What order you do then in. Tell the common user what happens, and what you expect. Tell us if anything you're using is beta or canary. Then us non-genius common users can try it. And if it happens to us.. we will elect you president. Until then, only a few of you have an issue, and a whole bunch of people think this might have happened to them on Tuesday.., but they're not sure.

I'm sorry. I've read all the posts.. on many of the forums. I've tried to follow the issues and test it on my device. I can't. So... Think like a tester and provide a repro, with serious repro steps.

Big deal? Maybe not to you but for some yes.

While it may not be a huge thing it is something that shouldn't be happening. In 2012? Maybe. 2018? Apps closing while doing 2 or 3 things? Ehhh... expectations are higher. People complaining like this and bringing it to light brings it to Google's attention and allows them to fix it. It is a good thing.

 

[SteelGator]

i would have just turned the podcast back on... And moved on. Is this really a big deal.? I am sure there are memory combinations and app combinations that will cause someone to lose thousands of dollars, or, heaven forbid, someone to lose their life. Though i would argue..." Why are you using a phone app to do this". But to the common user, trying to play music and watch a video while taking a pic and using my BT head set and navigating Waze on Android auto and an app closed so I'm pissed... Doesn't do it. Want to prove it to the common user, first caLm down and get off your soapbox. Then be very clear about what you're doing, what apps you're running, what versions you're running. What order you do then in. Tell the common user what happens, and what you expect. Tell us if anything you're using is beta or canary. Then us non-genius common users can try it. And if it happens to us.. we will elect you president. Until then, only a few of you have an issue, and a whole bunch of people think this might have happened to them on Tuesday.., but they're not sure.

I'm sorry. I've read all the posts.. on many of the forums. I've tried to follow the issues and test it on my device. I can't. So... Think like a tester and provide a repro, with serious repro steps.

Glad you decided to write such self-righteous, condescending post -- hope you felt better afterward. This is a thread about memory issues. Specifically, an issue that kills audio playback when taking a picture. I was relaying my experience, which I had only read about until yesterday. I gave a few specifics about why I had audio going when I took a picture. This is the intent of the thread, if you are not interested, maybe you should stop reading it?

I did turn the podcast back on, you brought all the drama to it, not me. I was not on a soap box, nor did I say I was pissed. I am not a tester, and I don't want to prove it to anybody, I am sharing my experience -- participating in an ongoing conversation and on topic. There is nothing in my post that warrant your attack. You must be a gem IRL.

 

[YankInDaSouth]

For my typical use I've not been having any issues ... yet. But I did have to test this out ... naturally, of course LOL.

I had navigation & Google Music going - opened the camera and started snapping pics. Wasn't until the 5th pic that Maps and GPM stopped. Only did that one "test" as those are likely the most resource intense apps I have on my phone. In all my years of "Androiding" I don't think I've ever been in a situation where I had to take pictures while using maps and GPM. I am not gamer nor do I generally use apps that require a lot of resources. So for me personally this has not been an issue, thus far (not even a week into using my new P3).

I know we all use our devices differently and I can certainly see how this could negatively affect power users so hoping Google addresses it quickly so people aren't put off by this and can enjoy what is an otherwise awesome phone IMO ...

 

[Mike Dee]

For my typical use I've not been having any issues ... yet. But I did have to test this out ... naturally, of course LOL.

I had navigation & Google Music going - opened the camera and started snapping pics. Wasn't until the 5th pic that Maps and GPM stopped. Only did that one "test" as those are likely the most resource intense apps I have on my phone. In all my years of "Androiding" I don't think I've ever been in a situation where I had to take pictures while using maps and GPM. I am not gamer nor do I generally use apps that require a lot of resources. So for me personally this has not been an issue, thus far (not even a week into using my new P3).

I know we all use our devices differently and I can certainly see how this could negatively affect power users so hoping Google addresses it quickly so people aren't put off by this and can enjoy what is an otherwise awesome phone IMO ...

I've only tested with running any two of those and not experiencing any issues. I used to have an issue with the music apps and camera but the phone seems to have learned to be able deal with it after I disabled adaptive battery on music apps for a few days and then restored it. It would ba a rare moment for me to listen to music and use the camera anyway. I do run GPS on the phone or AA and music at the same time and it's never an issue. Snapping pictures while doing the other two would never happen in my life and In earlier versions of AA the phone used to prevent that. Also not a good a idea if a driver is doing that but that's a whole different topic.

 

[SteelGator]

Snapping pictures while doing the other two would never happen in my life and In earlier versions of AA the phone used to prevent that. Also not a good a idea if a driver is doing that but that's a whole different topic.

Very true Mike, but don't forget, you can be the passenger (or have a passenger to help) and want to use your phone for each item as well -- one of the reasons I get frustrated by all the limitations put on phones when in AA. Anyway, you are correct, this is a whole other topic indeed. (sorry, just frustrated by the nanny state, lol)

 

[Mike Dee]

Very true Mike, but don't forget, you can be the passenger (or have a passenger to help) and want to use your phone for each item as well -- one of the reasons I get frustrated by all the limitations put on phones when in AA. Anyway, you are correct, this is a whole other topic indeed. (sorry, just frustrated by the nanny state, lol)

I didn't forget.... That's why I mentioned driver specifically. I assumed the passenger option was a given.

 

[mustang7757]

I've only tested with running any two of those and not experiencing any issues. I used to have an issue with the music apps and camera but the phone seems to have learned to be able deal with it after I disabled adaptive battery on music apps for a few days and then restored it. It would ba a rare moment for me to listen to music and use the camera anyway. I do run GPS on the phone or AA and music at the same time and it's never an issue. Snapping pictures while doing the other two would never happen in my life and In earlier versions of AA the phone used to prevent that. Also not a good a idea if a driver is doing that but that's a whole different topic.

I feel the same way, after learning here that taking a picture and playing you tube kicked me out of it I'd never use my phone that way, now using phone on a call and going into different app I've done without issues or using maps and another app.. but onced adaptive battery learned the YouTube and camera same time it didn't force close it any more . Guess with machine learning you have to teach your device now how you use it.

 

[Rukbat]

We're talking Pixel 3 phone right? Not Pixel 3 mainframe?

Phones can run 2 or 3 apps at once (depending on the phone and the apps) but not all app combinations. Apps aren't written for Pixels, they're written for Android, and some of them just stop when they're not the foreground app, for a few reasons (some of which make sense to the developer - and to half the users, but not to the other half of the users).

We can send MMSs to other carriers (we couldn't when MMS first came out), we can run some combinations of apps (we couldn't at first), one day, maybe phones will have the equivalent of 16GB of RAM, and we;ll be able to do without desktops, laptops and anything but phones. But not yet. I don't think the fact that we're not there yet deserves a fight or snide remarks.

 

[ClintRo]

It is not inconceivable that you would use YouTube and then want to take a picture. Then when you go back too YouTube only to find that it closed.... Sometimes not saving your position in said video. It is an annoyance that's we shouldn't have on the Google Flagship phone.

 

[Mike Dee]

It is not inconceivable that you would use YouTube and then want to take a picture. Then when you go back too YouTube only to find that it closed.... Sometimes not saving your position in said video. It is an annoyance that's we shouldn't have on the Google Flagship phone.

Just tried that....YouTube was right were I left it after I took pictures. It won't run in the background without a subscription. Having tested it, I normally don't do it and it didn't crash. If it did stop from memory after opening a few apps it personally wouldn't matter that much too me. If it matters to someone else it is certainly important to them but I'm not about to worry about how many apps have to reload after opening a few. Just how many is a good number?

 

[ClintRo]

Not sure... But I have had it happen to me... It is an annoyance. Never had that issue on my phone's before. FYI I do have the subscription and do use YouTube in the background a lot.

 

[Mike Dee]

Not sure... But I have had it happen to me... It is an annoyance. Never had that issue on my phone's before. FYI I do have the subscription and do use YouTube in the background a lot.

Try disabling battery optimization for the YouTube apps and restarting your device. I ran my music apps like that without a hitch for a few days and then restored it. Worked wonders for me even though realistically I rarely take pictures while listening

 

[Caezar07]

Though i would argue..." Why are you using a phone app to do this".

Really? Why are you "arguing" over how a person should use their phone.

 

[Caezar07]

This is a thread about memory issues. Specifically, an issue that kills audio playback when taking a picture.

Seems like there are just as many people in this thread that are here to play defense for Google and tell others that their problems are not valid rather than being helpful all because the Pixel 3 is faster than the galaxy s4 that they upgraded from.

And on replicating the issues....I can only sometimes replicate the memory issues very easily. More often issues came up when I was say 20min+ into a car drive using navi and music streaming at the same time....or say 10 minutes into a youtube video streaming in the background while using chrome or other apps. I think what's happening is that app is increasing it's memory usage along with me opening more browser pages and other apps.

I could replicate the camera issue, but initially the camera issues weren't even what brought me to this thread, it was just day to day use of navi and music/video streaming.

 

[Almeuit]

We're talking Pixel 3 phone right? Not Pixel 3 mainframe?

Phones can run 2 or 3 apps at once (depending on the phone and the apps) but not all app combinations. Apps aren't written for Pixels, they're written for Android, and some of them just stop when they're not the foreground app, for a few reasons (some of which make sense to the developer - and to half the users, but not to the other half of the users).

We can send MMSs to other carriers (we couldn't when MMS first came out), we can run some combinations of apps (we couldn't at first), one day, maybe phones will have the equivalent of 16GB of RAM, and we;ll be able to do without desktops, laptops and anything but phones. But not yet. I don't think the fact that we're not there yet deserves a fight or snide remarks.

But what you're saying isn't even close to reality. Majority of apps can be run in the background especially things like music apps so the issue isn't the app.

I get trying to defend but let's not pretend it's 2008 because.. it isn't. These apps aren't doing something new by running in the background.

 

[Rukbat]

Many (I won't say most - I haen't used most) music apps and many video apps stop when they aren't the foreground app. But the way I hammer my phone, with half a dozen active (even if not running) apps in RAM, I don't see a problem. Maybe it's peculiar to the Pixel 3 and 3XL - I can't address that.