Fixed
Status Update
No update yet.
Comments
cp...@google.com
sh...@google.com
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
yl...@google.com
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.
am...@gmail.com
FYI this memory leak also seems to exist when using the new FusedLocationProviderClient. I took Fernano's sample from
yl...@google.com
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.
am...@gmail.com
I am also still experiencing this!
yl...@google.com
Still present in 'com.google.android.gms:play-services-location:17.0.0'
As an alternative I am using FusedLocationProviderClient with PendingIntent:
IntentFilter intentFilter = new IntentFilter(ACTION_LOCATION);
registerReceiver(locationReceiver, intentFilter);
mFusedLocationClient.requestLocationUpdates(mLocationRequest, locationPendingIntent);
and
unregisterReceiver(locationReceiver);
mFusedLocationClient.removeLocationUpdates(locationPendingIntent)
Here is forked LocationUpdates repo with LeakCanary installed and an option to switch between LocationCallback and PendingIntent. LeakCanary not reporting anything when using PendingIntent.
https://github.com/dejandobnikar/location-samples/tree/master/LocationUpdates
As an alternative I am using FusedLocationProviderClient with PendingIntent:
IntentFilter intentFilter = new IntentFilter(ACTION_LOCATION);
registerReceiver(locationReceiver, intentFilter);
mFusedLocationClient.requestLocationUpdates(mLocationRequest, locationPendingIntent);
and
unregisterReceiver(locationReceiver);
mFusedLocationClient.removeLocationUpdates(locationPendingIntent)
Here is forked LocationUpdates repo with LeakCanary installed and an option to switch between LocationCallback and PendingIntent. LeakCanary not reporting anything when using PendingIntent.
am...@gmail.com
Thank you for your feedback. We assure you that we are doing our best to address all issues reported. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with the bug report here https://goo.gl/TbMiIO and reference this bug for context.
yl...@google.com
ga...@linecorp.com
ga...@gmail.com
ga...@linecorp.com
yl...@google.com
There is an issuetracker Component available these days for Play Services Location:
Maybe move this issue to that Component to track it better?
ga...@linecorp.com
I can't move it right now, but I think it's ok to stay here.
As I wrote in the code lab issue, I misunderstood when the rewrite went out (which should fix the issue).
It goes live in version 20 (current version location 19.0.1). The engineer who wrote the rewrite checked and wasn't seeing the same issue, i.e., it should be resolved.
However, that does mean we have to wait until 20 is released. I can check in again here when it's live for you to double check.
ga...@linecorp.com
8 ram
yl...@google.com
I haven't been on location in awhile, but I wanted to follow up on this.
The issue should be resolved with
yl...@google.com
Added workarounds in
Description
I have released a new version of my application in beta track and started receiving lots of crashes from liblanguage_id_jni. It is used for auto-detection of sentence lang for TTS.
While not fixed maybe something can be done as a workaround?
Examples:
Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x7a71f4a0d636Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)ENVIRONMENT
CRASH REPORTS
Android 12 (Emulator)
Android 10 (Xiaomi Realme 6 Pro)
CODE SAMPLES
initialization:
usage (may be called from different threads):