K
The announcement of a static version of the OBD manager class or Shared, on the other hand, is likely to rid itself of extra leaks, you know, if you think it's static. In general, it depends on use. Liquid Shared I don't even know how static it is, but the OBD can actually do that on both the record and the reading. Well, for example, if you're gonna put the cadet down and don't shut it down, and in that case you'll get something like that. Object Sqlite.* was leaked! Please fix your application to end transactions in progress properly and to close the database when it is no longer needed. That's why even considering it, you can say it in the documentation. SQLite will never leak memory. This is true even in the face of memory allocation failures or other system errors. Shortly in Sqlite, there's no liquor memorial, if you even rig yourself. But sometimes you can meet, like, Leak found
Caused by: java.lang.IllegalStateException: SQLiteDatabase created and never closed
There are many approaches to using BDE Sqlite, but there are a couple of reports that indicate that the best way to ANdroid is to open it when it comes to launch (in the Application Class) and to close out. Otherwise, as much as you don't use the OBOs from different cones, you catch database is lockedSinglton, but you can speak. attempt to re-open an already-closed object: SQLiteDatabase I would therefore recommend that the early optimization of the OBD be avoided, especially in small applications. The static itself is terrible for the design of the project, in any case it's better not to use it.