Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Sample application, memory leaks found by LeakCanary

See original GitHub issue

Issue Type

[ X] Bug

Description and/or steps/code to reproduce the problem

I was using the demo application and noticed that LinearLayout is leaked when calling a sample and moving back to the ListView. I added screenshots from three different cases below.

Environment

If it’s a bug, version(s) of android this affects:

All

Version of osmdroid the issue relates to:

6.1.5

Screenshot_20191227-105837 Screenshot_20191227-105847 Screenshot_20191227-105909

Issue Analytics

State:
Created 4 years ago
Comments:15 (5 by maintainers)

Top GitHub Comments

1reaction

monsieurtanukicommented, Jan 19, 2020

So far so good. The solution seems to be:

in all Fragments, the Views must be nulled in onDestroyView (which is already the case in BaseSampleFragment because of an old memory leak issue #335)
a good practice seems to call the super statement last in onDestroyView

As there are about 140 Fragments in the demo app, the fix is not going to be instant (though it’s easy). I’m working on it.

0reactions

monsieurtanukicommented, Jan 20, 2020

Life is short: I limited the fix to the main Fragments. If we find fragments related memory leaks, now we now how to deal with them. Fixed by #1487.