IssueTracker

We have passed this to the development team and will update this issue with more information as it becomes available.

If you replace Google Music with Amazon Music in the above sequence Pixel 3 will stop playing the media on Amazon Music app.

Same issue on Pixel 2 XL, using to Ressource heavy Apps auch as maps navigation and SoundCloud causes one of them to get choppy and eventually killed, super annoying

You can also replace Google music or Amazon Music with Spotify to replicate the music. I've also had it happen with more specific media apps such as LivePhish

I confirm Pixel 2 XL as well

The issue is a prominent one. I have had music from other apps play in the background of other apps even after closing them. This is the same way with notification noises as well.

My google fit tracker shutdown and stopped recording my workout when I took a picture. Pretty sure it is related to this RAM management issue. I have the Pixel 3 XL.

Same things happened on Pixel 2 XL. Especially when I use camera. Taking pictures couse stop music apps and restart apps like accubattery.

Having the same issue on my Pixel 3 XL

I never comment, sorry people who get this by email:
Pixel 2 XL is like this for over a month, if not since Pie. Horrible lag and RAM management.

My Pixel 3 xl will shut down ALL background apps, including music, if camera or a game or even YouTube is launched

Just to confirm, this also happens on the Pixel 2. I can reproduce this by playing music via Spotify, launching the camera app, and taking 3 pictures. It starts to lag a lot then kills the music app.

### !!! ATTENTION !!! ####

If this impacts your device, please contribute to the conversation by answering the questions below.  If you cannot answer these, please do not contribute to the conversation. Each person who has starred this issue is notified of your contribution. Please consider others before posting a "me too" or "having the same issue over here!" response.

---

Android build
Which Android build are you using? (e.g. OPM1.171019.011)

Device used
Which device did you use to reproduce this issue?

Steps to reproduce
What steps are needed to reproduce this issue?
Please explain the reproduction steps in detail.

Expected output
Could you please explain the expected behavior.

Current output
Could you please explain the current behavior.

Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report  file to this issue.

Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.

Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue

Please get this resolved ASAP! Shouldn't have to pay 1k for a phone with a software issue as such.

Yes running Google map and my YouTube picture in picture mode got killed . Or Spotify sometime. And wechat have to be reopen so often.

Also my Pixel 2 XL reloads apps ALL THE TIME. It's much better to have the apps already open and ready to use, but I have to keep wait for apps to reload almost every time, it's very annoying.

Having this issue on pixel 3 xl as well as pixel 2 and pixel 1. All since Android pie. This is a pie issue.

I can confirm the exact same behavior on my Pixel 3 XL, build PD1A.180720.030

Having exactly the same issue on my pixel 3 128gb

After turning off the Adaptive Battery function, restarting the phone, the issue cannot be duplicated.

I am also having this issue. Walking to the gym the other day so I had navigation going and a podcast on stitcher. I stopped to take a photo of some street art and it killed my podcast.

I fought this issue a lot last weekend while tracking a hike with Alltrails and using the phone to take pictures in the stock camera app. Upon switching back to the Alltrails app after taking photos, I would find that my recording paused. It happened three times before I gave up on trying to record the hike at all.

Android build: PD1A.180720.030

Device used: Pixel 3 XL

Steps to reproduce:
1. Open Alltrails app. Start recording.
2. Open camera and take some photos.
3. Switch back to Alltrails to find that your recording has paused.

Expected output
Alltrails should continue tracking my progress in the background.

Current output
Android has killed the Alltrails app process, pausing my recording.

Seems to be an issue with Android Pie, can confirm issue on my Pixel 3 XL 64GB

This issue cannot be fixed by turning off adaptive battery and restarting phone. I tried this and it still happen with music apps and Pokemon go

IF YOU COMMENT ON THIS, EVERY SINGLE PERSON WHO STARRED IT GETS NOTIFIED, so kindly stop, unless it needs to he commented.

Adding to my previous comment....
---

Android build
PD1A.180720.031

Device used
Pixel 3 XL - Black

Activity Leading to Issue
-Listening to music on the app "LivePhish" (substitute with "Spotify" for same results)
-Apps open in background are as follows...
1.Outlook
2.Settings
3.Messages
4.Google Photos
5.Google Calendar
6.Chrome
7.Relay
8.ESL Mobile Bankng
9.Dark Sky
10.SnapChat
11.Instagram
12.Clock
-Camera is opened
-Photo is taken
-Music is stopped
-Music app is closed

The issue can also be replicated using the original method of playing media, using navigation, and opening the camera/taking a photo

Expected output
Apps continue to work in the background

Current output
Apps are failing to continue background services

Android bug report
https://drive.google.com/open?id=1-lbQcYpp3uRO8oNwZUYo3D-fjAR2pB6F.

Did not see it mentioned, so apologies if I missed it and this is redundant.  But Nathan Chancellor mentioned it might be related to the kernel changes in Pixel 3 which includes the use of the lmkd (low memory killer daemon):

https://twitter.com/nathanchance/status/1053896933327089664

Just figured I would throw it out there. Here's the content of the tweet:

2a. The memory issues that some people are complaining about may be due to the switch (https://android.googlesource.com/kernel/msm/+/2ec57a534a5eea1e43329134d19f76642d5081bf) to lmkd (a userspace low memory killer implementation, https://android.googlesource.com/platform/system/core/+/android-9.0.0_r12/lmkd/)

The Tile App need to run in the background for me to keep track of my belongings, but Android keeps killing it on my OG Pixel.

I fought this issue a lot last weekend while trying to listen to Spotify and using the phone to take pictures in the stock camera app. taking photos with the app my spotify would die and wouldn't even keep track of where my song left off. It has happened everyday if I take a photo and have spotify on.

Android build: PD1A.180720.030

Device used: Pixel 3 XL

Steps to reproduce:
1. Open Spotify app and start playing music.
2. Open camera and take some photos.
3. Spotify music stops and doesn't keep your spot.

Expected output
Spotify music should continue streaming throughout taking photos in the photo app

Current output
Android has killed the Spotify app and stopped playing music without saving my spot in the song.

I DO NOT have this issue on Pixel 2 XL running Pie with August security patch:
Android 9, August 5th, Kernel 4.4.116-gcff1ae5 ---- Build PPR1.180610.009

I VERY MUCH have this issue on Pixel 3 XL running Pie with September security patch:
Android 9, September 5, Kernel 4.9.96-g340a9aaf92bc-ab4959234 ---- Build PD1A.180720.031

For this reason my Pixel 2 XL is swapping apps much quicker, keeping more apps in memory, and is much more stable than my Pixel 3 XL.  Was this issue introduced in the September update?  Can anyone else with this issue on Pixel 2/OG confirm it was not occurring previously but now is occurring after September update?  Can you confirm kernel version on Pixel 2 as of September patch?

I have this issue on both the Pixel 3 XL and the Essential Phone (October security update).  The common denominator is Android Pie.

I have this issue with my Pixel 3. I put important apps on "Not Optimized" and opening the Camera app will cause it to wipe the apps from cache and have to reload.

My new pixel 3 shouldn't record worse audio than my pixel 2. I will be returning it soon if I don't see any up coming fixes for multiple issues

I also have this issue on my standard Pixel 3.

This is an issue I have as well, and it's really concerning to me. If I can't see proof that this is a fixable issue that Google can/will address through a software update in the near future, I'll have to return the phone. Disappointing since otherwise I really enjoy the phone, but I can't justify keeping it when phones like the OnePlus 6 are more affordable and don't experience these issues. Please fix asap!

Unfortunately have to unstar due to the high volume of low quality comments flooding my inbox.  Please follow the accepted bug report template of the OP or don't comment at all.

Android build
PD1A.180720.030

Device used
Pixel 3 XL

Steps to reproduce
Played music from Google Music App
Opened Google Maps (began navigation)
Switched to the camera to take a picture

Expected output
Google Maps navigation continuing on

Current output
Google Maps was killed.  Tried again, next time Google Music was killed.

Android bug report
Don't understand the directions.

Alternate method:
Don't understand the directions.

Screen Record of the Issue
Don't understand the directions.

Android build:
PPR2.180905.005

Device used:
Pixel 2 XL

Steps to reproduce:
1. Open Spotify. Play music.
2. Open Google Maps. Start navigating anywhere.
3. Open Google Camera. Take several pictures (one picture does not reproduce it, but a few pictures in succession does)

Expected output:
Music should keep playing in the background

Current output:
Android kills Spotify. Navigation is left unaffected.

Been having the same issues on my Pixel 2XL for awhile now, this needs resolved asap.

Yes, I moved from the Huawei P20 Pro on Oreo (which also aggressively shuts down apps to save battery) and the P3 XL is significantly worse.

As noted in the original bug... I also have seen maps exit while driving, which can cause a dangerous situation. IMO this should be a P1.

I also have never had issue with hangouts getting shut down on recent phones but it happens constantly on the P3 XL.

Removing my star.

DO NOT ADD USELESS COMMENTS THAT YOU HAVE AN ISSUE TOO AND SPAM EVERYONE.

I have same issues with opening Map directions, Google Play & Camera usage.

Same, really hurting my financial apps. Keep switching btwn 3 apps to pay bills. Crashes the other two over and over. Very annoyed

You don't need to open google maps. Just play Google Play Music, open the camera using the double press of the power button and your background music will stop.

happens on pixel 3 and pixel 2xl for me.

Pixel 2XL has been horrific on RAM management for about a month now.  I need to fully clear all open apps at least 3x a day with light usage.

on pixel 2xl as well

On Wed, Oct 24, 2018, 5:22 PM <buganizer-system@google.com> wrote:

Android build: PD1A.180720.030

Device used: Pixel 3 XL

Steps to reproduce:
1. Open Spotify app and start playing music.
2. Open camera and take some photos.
3. Spotify music stops and doesn't keep your spot.

Expected output
Spotify music should continue streaming throughout taking photos in the photo app

Current output
Android has killed the Spotify app and doesn't keep progress of the song.

This can also be reproduced by:
1. Opening maps
2. Opening Spotify(or anyother music app) and play music
3. take camera out to take a picture
4 close out camera app and other apps will close completely.

Expected: All apps function normally.

Current: Everything app is killed.

Device used: Pixel 3 XL 64GB

Steps to reproduce:
1. Open Spotify app and start playing music.
2. Open camera. (Not even take a photo all the time, usually just open the app)
3. Spotify music stops.

Expected output
Spotify music should continue streaming throughout taking photos in the photo app

Current output
Android has killed the Spotify app and doesn't keep progress of the song.

This can also be reproduced by:
1. Opening maps
2. Opening Spotify and playing music
3. Open Camera
4 close camera app and other apps will close.

Expected: Background apps continue to run

Current: Apps are killed too aggressively.

I picked up a demo pixel 3 xl in best buy, opened up the camera app and hello down the capture button to take a burst. The camera app died repeatedly after 9 or so photos. Definitely not interested in purchasing a device with this behavior.

Same with my pixel 3 XL. Was playing music in Saavn music app and tried to navigate using Google maps. Music app got killed. Same issue with vise-versa. The maps app was killed when I re-opened music app. Horrible RAM management.

"I picked up a demo pixel 3 xl in best buy, opened up the camera app and hello down the capture button to take a burst. The camera app died repeatedly after 9 or so photos. Definitely not interested in purchasing a device with this behavior."

Neither demo unit in the local best buy nor the 3XL I purchased have this issue with bursts - your example is anecdotal at best.. This issue tracker is to report the Pixel killing background apps too severely. Everyone keeps posting comments that aren't pushing the issue forward and everyone's email is blowing up.  If you're not giving an example of the issue in question, please don't post.

In my case, I'm seeing apps that just don't stay open as long as I'd like but it's not a huge issue. For instance, I open Reddit and browse then jump to Facebook then Instagram. Sometimes, when I go back to Reddit, it reloads the home page.

I don't have Spotify but when I use Apple music, I cannot recreate the issue as stated in this tracker. I don't have Spotify, so maybe it has to do with that app in particular. I opened Apple Music and started a song streaming. Then I opened maps and started navigation. I then opened the camera, took several pictures, looked at them and then deleted them. Everything was still going as I left it.

Again, I think the Pixel 3XL I have is killing apps a little too quickly but it's not a severe as reported here.

Android build: PD1A.180720.030

Device used: Pixel 3

Steps to reproduce:
1. Open Google Play Music. Play media.
2. Open Google Maps.  Start navigating somewhere (anywhere).
3. Open Google Camera. Take a picture.
4. Switch back to Google Maps.

Expected output
Google Maps should still be actively navigating me and music should still play

Current output
Music stopped when picture was taken. Android has killed the Google Maps app process thus ending your navigation session

@56

Do you mean this issue also occurs on the smaller Pixel 3 in addition to the larger Pixel 3XL?

I'm not 56 but I've certainly had it happen with my regular Pixel 3. Not as often from the sound of it but obviously it still gets old.

This is definitely an issue on the regular non-XL pixel as well.. I've confirmed across 3 different phones... Please update the title

Confirmed that turning off Adaptive Battery fixes this issue for me. With Adaptive Battery on, navigation + music + camera always kills navigation + music.

Confirmed issue.

Android build: PD1A.180720.030

Device used: Pixel 3 XL

Steps to reproduce:
1. Open Google Play Music. Play media.
2. Open Waze.  Start navigating somewhere (anywhere).
3. Open Google Camera. Take a picture.
4. Switch back to Waze.

Expected output
Waze should still be actively navigating me.

Current output
Android has killed the Waze app process thus ending your navigation session. Unable to reopen Waze app until phone was restarted. App hangs until forced to close by pop up.

I assume the camera app is one of the reasons here.

It makes my Pixel 2 XL lags and it also results in some apps reloading.

Issue ID for the 2 XL 118393019

This is not a app switching bug or memory management bug. It's simply a
memory leak that's causing this issue. My guess is camera (maybe AR?).

You can restart phone and it will hold a ton of apps in memory for a while.
Then over time it will get worse. I'm continuing to monitor but since
restart it's been working perfectly. I haven't used camera yet though.

All in all definitely think it's a leak and less some aggressive memory
killing config.


On Thu, Oct 25, 2018, 3:43 PM <buganizer-system@google.com wrote:

I thought it was background apps being the issue but based on my experience it's strictly the camera app to blame.

Google Pixel 3 XL
- Running Waze with battery optimization disabled
- Running Pocket Casts with battery optimization disabled
- Starting the camera app

If I have Motion Photo disabled everything works fine and I can take a picture with Waze and Pocket Casts running in the background and remaining in the background.

But if I have Motion Photo set to On or Auto and motion photo is recorded then all my background apps get killed.

So I think it has to do with memory demand of the motion photo not the camera app itself.

I have the motion setiing always set to off and I still have the memory leak. Pictures not saving, spotify closing when a pic is taken, apps being killed way too aggressively in background. It is not he motion setting.

Only reason I’m contributing to the noise is because this issue seems to affect more than the Pixel 2 or 3. Also it seems there are some red herrings about memory management suggested above.

build : OPWS28.3.4
Device: Moto X4 Android One Version

Steps to reproduce: Try to use any app that gets used in the background. Open the camera app.

 Expected Behavior. I understand this is an intended power saving “feature”. Unfortunately intelligent decisions made for users need to actually be intelligent 100% of the time. I was using GAIA for navigation in the backcountry. Now, this particular time I was familiar with the trail and am decent with navigation general. However, I’m sure there is someone out there that relies on this to figure their heading based on where they came from. This could mean some clown getting lost in the woods not just that their podcast app getting closed. My phone had 75% battery life when done a 12 hour hike. Great job, saved battery life, but I wanted navigation. I’m sure there are background apps that are needed. Another note: Even when I turned off “optimization” for Gaia mid hike I expected the app to still be able to parse the gps at regular intervals. Seems like it could not. (maybe unrelated seems like it could be)

This is what the track looked like after battery optimization for Gaia was disabled. Note: I did not hike in a straight line down the mountain. https://www.gaiagps.com/public/iE7eyWMzQ1SVrzNCezoZ7q2p

Android did gracefully close the app the first time, as evidence by the record of the first track
https://www.gaiagps.com/public/tXAS771Brn1v6g6L5uSN1iov

Actual behavior: Your app that you might be relying on gets killed. Happens more aggressively in cold weather (16 degrees fahrenheit ) when the battery drains faster.

Alternate behavior Case: I’ve also noticed after long periods of time in battery usage android would close Castbox. After about 1-2 hours in 60ish degree weather. GAIA was also running and did not get closed in this instance. Note: Camera app was not used in last case

Android Bug Report: I immediately could reproduce the issue with Nokia Here and the camera app, but there is no bug report directory on my device. Does the device need to be in dev mode? I think anyone working on this issue is going to get the idea of what is going on. Unfortunately a feature is turning out to be more of a bug. Happens all the time is software development. Roll it back and actually push a fix before it gets on more devices. I feel bad for all the app devs that have to field support questions about their apps “crashing” because of this. Most users must have no idea what’s going on. This is going to just make android look buggy in the eyes of the general public if it gets on to more devices.

In order to solve this issue, you guys increased the random access memory to 6GB in Pixel 4.

The other way to address this issue which feels to have been ignored since release is to choose another manufacturer. I am very disappointed with this "premium" phone I have purchased.

This issue has been addressed and I have not had any issues with it, what are you guys talking about?

Switching between Signal and Twitter while trying to use iHeartRadio and
the radio keeps getting killed. So yes there is still an issue.

On Fri, Aug 16, 2019, 8:50 AM <buganizer-system@google.com> wrote:

App killing is still an issue. Use Android Auto with Waze and Spotify running. Try to take a picture and see what happens. App killing is still too aggressive in certain instances.

I run a waze with google play music/youtube music without any issues since
all the updates.

On Fri, Aug 16, 2019 at 6:55 AM <buganizer-system@google.com> wrote:

--
Andrew Balingit
abalingit@gmail.com
650200DREW
Gooooooooogle Profile: Me! <https://profiles.google.com/abalingit>

I used to have the issue pretty frequently with Waze/Spotify/Camera, but
now the frequency has decreased significantly. Almost never, but every once
in a while, it still happens. I haven't identified a pattern yet for these
infrequent instances.

On Fri, Aug 16, 2019 at 6:59 AM <buganizer-system@google.com> wrote:

--
Trang Nguyen

Still an issue for me as well, last time a couple of weeks ago, tried to take a portrait photo while in a voice call in FB Messenger, my voice call was dropped.

Pixel 3 (not xl) running Android 9 - PQ3A.190801.002

If we're talking about how easy this is to reproduce. I can't play PokemonGo and stop to take a photo without it killing PokemonGo. This has been the case since I got the phone and has not gotten better.

I so desperately wish that I could mark particular apps as higher priority to limit how easily they are killed. Or if I could create some SWAP space that apps could use rather then being killed, that would also help so much.

Earlier this week I was using PocketCasts to listen to a podcast while cleaning my kitchen, I stopped to take a photo of my dog and it killed my podcast app. I've had that happen when opening maps while listening to podcasts on my bus ride home.

This happens so often to me I typically treat my phone like it can't do anything in the background. I've gotten a sense of which apps are most likely to kill other apps, but man it's painful.

I constantly have this issue when switching between google maps and spotify. Honestly it boggles my mind why a premium phone like the pixel 3 would ship with 4 gigabytes of ram.

I still have this issue. Most noticeable when Spotify crashes and mg music stops. It can be from anything, using the camera, opening a website sometimes I'm not even doing anything but something happens in the background and it crashes.

It happens with other apps too. Too many constantly have to reload.

4GB is just NOT enough. And it's also concerning the Pixel 4 will only have 6GB when everyone else has 8-12GB.

Still occurs, just occurs less often for me.

Google, you think I'm buying pixel 4 after this?

Maybe you'll fix this "priority 1" bug when pixel 5 comes out.

Get it together, or partner with a real manufacturer.

On Fri, Aug 16, 2019, 7:52 AM <buganizer-system@google.com> wrote:

Same here, I have almost given up with my pixel 3 XL now and use my note 7 on a daily basis. Please Google look at other manufacturers and how much ram these other devices include.

Want to chime in on this as well. This issue has not improved since launch. Music closes when using Snapchat and Camera. Absolutely unacceptable from a $999 phone. This will be my last pixel.

Haven't seen this issue in months. Happy here 3XL. Unsubscribing so I can ignore the people complaining.

I can't reproduce this on both a Pixel 3 and 3 XL, even with additional apps open. There needs to be another factor in play here. Perhaps there's another app running in the background.

Also, when the Pixel 3 launched, 4-6GB RAM was commonly found in high-end phones...and other 4GB phones do not have this issue. It's safe to say it's a software bug--not hardware.

I still see it as well, but I have just accepted it as a horrible decision on my part. But this isn't the only issue. The lagging (especially of the camera) is horrible. Plug in to Android Auto and good luck launching music or YouTube (to listen to not watch on the road) without waiting forever or dealing with a crash. It's just not a good phone really. It does take fantastic photos when you can get the camera launched.

Things are still bad here too. Android Auto seems to be a huge culprit.
Things are usually a little better unless I'm using it. When using it the
camera is the kiss of death for everything else including navigation.

On Fri, Aug 16, 2019, 8:39 AM <buganizer-system@google.com> wrote:

I returned my pixel 3xl and bought an IPhone XS Max. The poor ram
management was too much to deal with. Love to software, hate the hardware
of the pixel line.

On Fri, Aug 16, 2019 at 12:08 PM <buganizer-system@google.com> wrote:

I experience issues with this daily. I cannot listen to YouTube Music or Google Play Music and take even a single picture with the camera app. The music apps close in the background and often my queue of music is gone. This is a huge issue for me.

There were a few months where it didn't happen often, but about 2 months ago the issue came back with a vengeance.

We need a real solution for this! 4GB should be enough ram...the Pixel 2XL had 4GB and I never had this issue.

Ever since I disabled Digital Wellbeing things have improved greatly but it's not perfect.

Have those of you who have had Android auto related issues had any issues with the new Android auto? It seems to be much faster and snappier

Optional

Our Engineering team is still working on this issue. We will provide more updates as they become available.

It's been almost a year since I psid $1k for this phone, and this supposedly Priority 1 issue STILL persists. This really strains my faith in either Google's desire to fix this problem, or Google's ability to fix this problem. The release of Android 10 has made things better, but has not resolved the issue.

@91
It is not fixable thanks to the 4 GiB only ram.
The next pixel 4 solves the problem by increasing ram to 6 GiB, while the mainstream value has raised to 8GiB.

disclaimer: All phones with 5G capability released by now come with a 12 GiB ram configuration where 4GiB is solely used by the 5G baseband and is not visible by the Android system, so these phones are also considered as the mainstream 8 GiB ones.

It is worthless talking about its price, everyone here who owns a pixel 3 has paid that much.

Really unhappy with Google's response to this.  No pixel 4 for me.  It's
about to be released and you guys can't stop apps from killing themselves.

Do I really want to be on the cutting edge of your software?  I think the
word is beta tester.  I am overwhelmingly disappointed by your response to
this.  It's basically a "sorry, you already paid us, loser."

Of course you can't actually admit there is a serious issue, because then
you'd be forced to do something about it.

I'm either going back to iPhone or swapping to another manufacturer.  Get
your game together.  Maybe hire another developer or two.




On Thu, Sep 19, 2019, 9:33 AM <buganizer-system@google.com> wrote:

"Our Engineering team is still working on this issue." Almost one year after the phone came out. I have no idea how your phone testers didn't come across the apps being killed so often. It's really frustrating for a flagship phone to do this. Also given the cheap price of RAM, i'd love to know why this flagship didn't come with more.

@ #94

RAM isn't actually cheap but the Pixel 3 isn't a cheap phone either

It's likely a big engineering task requiring changes over many. For me the issue has gone from really terrible to bad. There's a lot of room for improvement still but the work that's been done has been significant. My phone currently has an uptime of 14 days. On P I'd have to restart it every day (may twice sometimes) for it to be useable!

I'd like to send a thank you for your continued improvement to the engineering teams.

Thank you for your constant feedback. We assure you that we are continuously making memory improvements, some of which have begun rolling out to users in the latest versions of Android 10. If however you are still experiencing this issue on the latest versions of Android 10 (e.g. QQ1A.200205) , please capture and attach bugreports here so that we can look into what additional changes we can make.

The latest version of Android R continues to make improvements to memory management that began with Android 10. If you'd like to get a sneak peek you are welcome to try out the Android R Developer Preview at: https://developer.android.com/preview and provide feedback relating to memory management or anything else at: https://developer.android.com/preview/feedback. Thanks for all the feedback on this issue.

Has anyone noticed any improvement with app switching after the January 2021 update?  The update notes aren't very precise but there is a "Fix for issue causing intermittent restarts in certain apps" for pixel 3 and up.