Also if you are keeping an open cursor or client reference on the bookmarks content provider, I would really recommend against that, since that requires that the browser stay running as long as your app is (and the browser can use a lot of memory). Also as you have seen, if it does get killed, any apps that are currently using it also get killed as well.
On Mon, Sep 7, 2009 at 8:20 AM, Mark Murphy <[email protected]> wrote: > > r3 wrote: > > when i run my application for long time then my applicatiojn gets > > killed: > > > > i always get the same logs which are attached with this post. > > > > kindly help me out... > > <snip> > > > I/ActivityManager( 587): Low Memory: No more background processes. > > Something on your device or emulator is leaking memory. Eventually, > Android has to start killing things off to free up memory, and > eventually that causes com.android.Browser.BrowserProvider to be killed, > which kills your application. > > Use DDMS to identify what application is leaking memory. If it is yours, > fix the leak. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://twitter.com/commonsguy > > Android Training in Germany, 18-22 January 2010: http://bignerdranch.com > > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
