tag:blogger.com,1999:blog-8001153144156969687.post1228061785201273594..comments2024-03-28T02:24:51.130-05:00Comments on Daniel Lew's Coding Thoughts: ViewFlipper and Memory LeaksDanielhttp://www.blogger.com/profile/17003436808680466962noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8001153144156969687.post-13873650133339174452010-03-08T12:59:23.056-06:002010-03-08T12:59:23.056-06:00It keeps a hold on itself by using a handler to me...It keeps a hold on itself by using a handler to message itself at a later date.Danielhttps://www.blogger.com/profile/17003436808680466962noreply@blogger.comtag:blogger.com,1999:blog-8001153144156969687.post-85559535435842169142010-02-27T14:33:31.355-06:002010-02-27T14:33:31.355-06:00"So the ViewFlipper keeps a hold on itself an..."So the ViewFlipper keeps a hold on itself and its children".<br /><br />I don't quite understand this sentence. If an Activity is destroyed, there will be no reference to the ViewFlipper object, so the ViewFlipper object in the Activity will turn garbage collectible. How can ViewFlipper keeps a hold on itself?Unknownhttps://www.blogger.com/profile/07873186850205896964noreply@blogger.com