Out of memory exception on setting wallpaper

by Romain Guy » Fri, 13 Mar 2009 00:27:02 GMT

Sponsored Links
 getWallpaper() is not leaking. The default Home app is using it and
does not experience out of memory errors because of that.

I am more than willing to fix any existing memory leak in the
framework (and I did several times) or in the default apps (and I did
several times) but developers should really stop assuming that out of
memory errors are always caused by the framework. It is *very* easy
for an application to leak or simply to use too much memory.

Romain Guy
Android framework engineer

Note: please don't send private questions to me, as I don't have time
to provide private support.  All such questions should be posted on
public forums, where I and others can see and answer them


Other Threads

1. now that nothing interesting can be done with audio in 1.0...

That is, no reading from any kind of byte stream, ie.
AudioInputStream, when can we expect this promised functionality.
It's the one thing that really interested me in Android and I'm really
sorry to see it go.  Any ETA or news about when this will become
available?  I haven't seen anything in the road map beyond the 1.0

2. Comming back to your application from a phone call

I have a problem with the new android 0.9 version.
In the previous version when I lauch from my application the execution
comes back to my application after I finish the call. But with the new
version a "Call log" application appears, I need to press the back
button to return to my application.
How can I come back to my application automatically once the call has

I'm launching the call in this way:

  runOnUiThread(new Runnable() {
            public void run() {
                Intent intent = new Intent(Intent.ACTION_CALL,


3. Irda support

4. Sensor values returned by tricorder

5. How can get the source code of the embedded app Pictures?

6. Android Maps application source code

7. Parsing a complex Dataset(containing diffgram) using SAX parser