Fixed
Status Update
Comments
br...@google.com <br...@google.com> #2
A link to another sample project demonstrating that the leak only happens when using: LocationServices.FusedLocationApi.requestLocationUpdates but does not happen using a deprecated method: googleMap.setOnMyLocationChangeListener.
https://github.com/fernandospr/android-maps-userlocation
rc...@gmail.com <rc...@gmail.com> #3
Hello, I'm also experiencing the memory leak in my activity responsible for the location service.
The implementation of my project is not different from the example project attached by fernando.
The implementation of my project is not different from the example project attached by fernando.
[Deleted User] <[Deleted User]> #4
FYI this memory leak also seems to exist when using the new FusedLocationProviderClient. I took Fernano's sample from comment #2 and hacked it up to use the FusedLocationProviderClient and was still able to observe the leak upon exiting the activity.
lm...@google.com <lm...@google.com> #5
Leak still present in 2019 on latest play-services-location 16.0.0. 3+ years since first reported via linked Github issue, no fix or hint of acknowledgment. Clown college grade software engineering.
lm...@google.com <lm...@google.com> #6
I am also still experiencing this!
Description
1. Create an Activity the MapView widget in it.
2. Call all lifecycle methods and the getMapAsync() to actually load the map
3. In the callback provided to getMapAsync() call googleMap.moveCamera(CameraUpdateFactory.newLatLngZoom(position, zoom)); with an arbitrary position and zoom.
4. Uninstall/deactivate the Google Maps app
5. Open you app and click on the button inside the MapView to open Google Maps.
Expected behavior:
The "Open Google Map" button is not visible or when you click on that button nothing happens.
Actual behavior:
Fatal Exception: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.VIEW dat=geo:40.8318524,14.339633999999933?z=16.0 flg=0x10000000 pkg=com.google.android.apps.maps }
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1663)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1431)
at android.app.ContextImpl.startActivity(ContextImpl.java:1254)
at android.app.ContextImpl.startActivity(ContextImpl.java:1236)
at android.content.ContextWrapper.startActivity(ContextWrapper.java:330)
at maps.ei.bt.a(Unknown Source)
at maps.ei.bt.a(Unknown Source)
at maps.ek.d.a(Unknown Source)
at maps.ek.g.onSingleTapConfirmed(Unknown Source)
at maps.dc.f.onSingleTapConfirmed(Unknown Source)
at maps.dc.g$a.handleMessage(Unknown Source)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5584)
at java.lang.reflect.Method.invokeNative(Method.java)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1268)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1084)
at dalvik.system.NativeStart.main(NativeStart.java)
Also add the following details:
- Device (and version of Android) you have verified this issue on: All
- Google Play Services client library version: 8.4.0
- Google Play Services version on the device: 8703034
- Android SDK Version: target 23