Hi,
I spent some time tracking down a database leak that I couldn't figure
out, until I decided to log all database open()s and close()s.
It turns out that I had a NullPointerException in my code which was
preventing the close().
I fixed this by moving the close() to a finally {} block - which
should be best practice, I guess.However, I think there should be an option to trap uncaught RuntimeExceptions in Services, just as they are done in Activities. What do you think? -- 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
