Ok, I believe I have fixed it by every time I need the database creating it and then closing it immediately afterward. Seems obvious I guess - don't leave an open database floating around.
On Jan 14, 12:33 am, 3D <ernestgfre...@gmail.com> wrote: > anyone else getDatabaseLeakfound in LogCat? What does it mean? > Thanks. > > On Jan 10, 2:43 pm, 3D <ernestgfre...@gmail.com> wrote: > > > In LogCat I keep gettingDatabaseLeakfound. The 'tag' isDatabase > > and the 'message' isLeakfound. And its followed by many lines of > > red in LogCat. > > > I'm using an SQLiteDatabase and I access it from two Activities and > > one Service. In the Service I explicitly close both the cursor and > > then thedatabasesince I can't use startManagingCursor in there. In > > both Activities I open thedatabasein both onCreate and onResume and > > close in onPause. In one Activity I also use a cursor with > > startManagingCursor to manage that for me. > > > So what is going on here? My app seems to be working almost all the > > time but the "DatabaseLeakfound" is very disconcerting. Thanks in > > advance. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
