Comments on: Avoid memory leaks on Android

By: Barb

Barb — Fri, 21 Jan 2011 05:18:33 +0000

Hello all from Barb Stevens even as carcinoma of the lungs is on the increase Adultfriends. Those short conversations you can only have with a try mortal and/or individual of the word adultfriends.

By: Linan Wang

Linan Wang — Mon, 17 Jan 2011 23:24:59 +0000

what if:
… there is a static method: Application.getCurrentApplication() ?!
… methods/constructors are designed clearer: don’t ask for Context if what really want is Application ?!
… do house cleaning in Activity.onStop(), clean up all such setCallback(null) things?
… mention the setCallback issue in the documentation?
… use weakreferences when necessary?

I have to say, no matter how much i like google, comparing with iOS, Android is just a third rate product. No taste in UI, nor in programming.

By: free tattoo stencils

free tattoo stencils — Mon, 10 Jan 2011 02:59:03 +0000

Just would like to say this blog is incredibly good. I always like to study some thing new about this since I have the similar blog in my Region on this subject so this help´s me a lot. I did a research on a theme and found a excellent variety of blogs but absolutely nothing like this.Thanks for sharing so much inside your blog.

By: glguro

glguro — Mon, 22 Nov 2010 10:46:19 +0000

The framework is suck,if they use a weakreference for mCallback then those leak will be never happend.

By: Android: Memory Leaks on Orientation Changes – Ben Oberkfell

Android: Memory Leaks on Orientation Changes – Ben Oberkfell — Thu, 14 Oct 2010 15:16:32 +0000

[...] hours of searching I found a tiny explanation in Romain Guy’s blog. There are two easy ways to avoid context-related memory leaks. The most obvious one is to avoid [...]

By: химчистка ковров библиотека имени ленина

химчистка ковров библиотека имени ленина — Mon, 27 Sep 2010 08:01:21 +0000

vmnb,m xcgjkvhbjn xdgfhjlk вымыть стекла в доме офисе и квартире

By: web cam girls

web cam girls — Sat, 21 Aug 2010 03:13:23 +0000

I love what I find here. I’ll come back. Thanks!

By: Eneko

Eneko — Fri, 06 Aug 2010 07:31:30 +0000

Are these considerations also applicable to static Bitmaps used, for instance, in ImageView.setImageBitmap, or only to drawables?

The fact is that my application uses very frequently some icons that are requested via Web Service. I am currently storing these images in a static Hashtable (using the URL of the image as its key and the Bitmap as the value) and using them in some Views, but I am afraid I am leaking memory this way.

Thank you in advance.

By: Рецензії

Рецензії — Sun, 27 Jun 2010 09:43:32 +0000

Занимательно тут у Вас. ) Надо будет еще заскочить.

By: Silknet

Silknet — Wed, 16 Jun 2010 09:34:19 +0000

P thanks to your ideas , iТd adore to adhere to your weblog as usually as i can.possess a good day