Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
im pretty sure this is a memory leak but no idea how to fix it
screenshot of eclipse memory analyser (Listener is a service started by an activity, airplaneWait is a BroadcastReceiver)
airplane wait is started in a thread, in Listener’s onCreate().
private IntentFilter ftrAirplaneModeChanged = new IntentFilter(Intent.ACTION_AIRPLANE_MODE_CHANGED);
.
registerReceiver(airplaneWait, ftrAirplaneModeChanged);
cheers for any help,
ng93
I don’t think it’s a memory leak. I think it’s just an artifact of the memory analyzer presentation of the object.. airplaneWait has a reference to this$0 , which in turn has a reference to the same airplaneWait object, so you’re really seeing the same objects over and over here rather than a huge number of different objects. The gui can’t differentiate between “contains a …” and “has reference to a …”
One of those is probably an inner class of the other. Non-static inner classes have implicit references to their parents.