topic Leaking LocationListener in LocationDisplayManager in ArcGIS Runtime SDK for Android Questions

Leaking LocationListener in LocationDisplayManager

LukaszSzczyglowski — Fri, 28 Nov 2014 14:34:54 GMT

Hi guys,

I have found out that once the .start() method has been called on the LocationDisplayManager class, the inner LocationListener is not unregistered from the LocationManager even if the stop() and/or pause() methods have been called.

This triggers really bad leaking flow leading to an issue, that even the Context itself cannot be garbage collected.

Looking forward to your responses.

Regards,

Lukasz

Re: Leaking LocationListener in LocationDisplayManager

GSauers — Tue, 17 Mar 2015 13:03:18 GMT

I am seeing the same issue in my application. A solution is needed ASAP. I am using ArcGIS SDK 10.2.5.

Thanks.

Re: Leaking LocationListener in LocationDisplayManager

DanO_Neill — Tue, 07 Apr 2015 23:43:36 GMT

I have confirmed and reproduced the issue and we are working on a fix.

Re: Leaking LocationListener in LocationDisplayManager

DanO_Neill — Thu, 30 Apr 2015 01:36:46 GMT

The issue I found is that the LocationDisplayManager was not reallocating resources when .stop() was called. This amounted to ~2MB of memory overhead. The bigger issue was that the app would continue to consume memory. We have a fix that reallocates memory back and ensures the app responds to garbage collection of which it did not before.

Regarding the Context not being garbage collected, this is because the Context is tied to the MapView whether directly or in relation to it's corresponding layout.

The fix will be in the next minor release ArcGIS Runtime SDK for Android, v10.2.6.

Re: Leaking LocationListener in LocationDisplayManager

GSauers — Thu, 30 Apr 2015 11:55:48 GMT

Great, thanks Dan.