Reloading google.com ~200 times creates 2k instances of LocationProviderGmsCore |
||||||
Issue descriptionI am not sure if this is expected. I am trying to investigate issue 633512 and I found that reloading google.com so many times causes too many instances of LocationProviderGmsCore. The retainers are: Path Element (rooted) ROOT → new root com.google.android.gms.location.internal.zzau@12cbe240.zzaRJ → new com.google.android.gms.internal.zzbee@12e2eab8.zzaRz → new com.google.android.gms.internal.zzbeg@12e2eaf0.mListener (dominator) → org.chromium.device.geolocation.LocationProviderGmsCore@12cce058 There are also 1000 instances of class com.google.android.gms.internal.zzbeg It looks like the location requests are not cleared?
,
Nov 10 2017
,
Nov 10 2017
Added to backlog hotlists.
,
Nov 15 2017
ssid would you help us understand how to reproduce this? We tried some direct attempts and logging and were unable to see multiple instances be created.
,
Nov 30 2017
ssid Friendly ping -- we need to know how to repro this -- we didn't see how it would be happening when looking at code.
,
Dec 7 2017
Sorry, I was ooo. I will try to reproduce it again and upload a java heap dump. I am missing the heap dump right now.
,
Jan 17 2018
Hi ssid, any luck reproducing this issue?
,
Mar 20 2018
Yeah i tried again and wasn't able to reproduce. Closing this for now. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mcasas@chromium.org
, Nov 9 2017Owner: ----