I've leaked a UI reference across a flip boundary. Are there any development tools I can bring to bear on finding the leak?
I've leaked something. My app's heap gets larger and larger on each flip. I've combed through every object I can think of looking for references that cross the flip boundary. It's a bit complicated because the app, and services it relies on are web-service driven and highly asynchronous; there's three or four services running at any given time; and part of the object model is preserved using . But I'm pretty sure it's not something in my object model. At this point, I'm fairly certain I've used a context incorrectly somewhere. Are there tools for navigating references on Android platform? I know Java//Eclipse has good tools for this. But the DDMS heap tools seem .... well... they don't seem to provide reference tracing tools that Java platforms do. Not that I can find, anyway.. Is there any way to attack this that makes sense? I've spent weeks on this, looking for the reference leak. It's killing me. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
