-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory leak class DelegatingOnCameraChangeListener i #54
Comments
I wrote the project at work today, and you will be able to switch to google maps' map view to see what I am talking about. I have to wait until monday for my admin to check it before I can do the pull request (it is a compagny related work). Sorry for the incoming delay. |
Hi, I have just added a .zip file (here) of the project. Sorry for such a huge file, be assure that there is no security issue or compromising file in the .zip . It is the easiest way for me at this time of writing. |
Hi mg6maciej. Did you have the time to look it? |
First of all thank you for this library. I have been able to flawlessly add more than 5000 markers on the map. Yet, when I rotate the device, I have a memory leak. I changed the code to use only the googlemaps one without the elements of AME and I didn't have any memory leak while rotating the screen (yet I can't add that more markers with such fluidity).
Here is the Java Heap Dump capture:
When I make a right click and jump to source it brings me here:
Keep in mind that in the destroy view of the mapview I use this (to make sure every thing is cleaned) :
Here is the version that I currently use:
1- Is there anyway to fix that memory leak from the library side?
2- For all your handlers, can you use this, that uses weak references for its handlers to avoid any memory leak?
The text was updated successfully, but these errors were encountered: