| commit | 6728ebfa9282a12ec437e8b878ab9e60be97b22a | [log] [tgz] |
|---|---|---|
| author | Vasu Nori <vnori@google.com> | Thu Sep 16 09:57:42 2010 -0700 |
| committer | Vasu Nori <vnori@google.com> | Thu Sep 16 09:57:42 2010 -0700 |
| tree | 749de3e307ff2070c8af9728bae267d5114e4f6d | |
| parent | e678f46ec45076203f6260f8a26f56d838c6b6ff [diff] |
STOPSHIP some debugging code to help find reproducible testcases sometimes mReferenceCount in SQLiteCloasable.java has some huge number (a memory address probably) this causes a database.close() or sqliteStatement.close() to randomly fail and not release the object. and that usually causes a finalizer warning or sqlite to return error "dbclose failed due to unfinalised statements" Change-Id: I392875b62ed270741633f5bffa519932e4a9f985