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.
I’ve read the official Android technical article: "how to avoid memory leaks ?". They say that creating inner classes in an Activity class is dangerous, but what about creating inner class inside a View class : is the leak danger the same or worse ?
If you create classes with lifecycle not more than view – it’s OK. Otherwise you should avoid doing this.
If you use such structure – be sure, that you do not have any links on instances of inner class, when view is not necessary. Then GC will collect everything, and there will not memory leaks.