History log of /frameworks/base/core/tests/coretests/src/android/content/ContentResolverTest.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
f90177629a5b69ca3a80466c0ab55abfeb6d26b2 01-Aug-2015 Abodunrinwa Toki <toki@google.com> Turn off failing tests in FrameworksCoreTests.

We want a green state so we can confidence in tests we write
going forward.

Change-Id: I2c8db848897b56d0c64202ad28861eb4a7572e07
/frameworks/base/core/tests/coretests/src/android/content/ContentResolverTest.java
872a52c6b637faf75262b83fe68ff4e0d9fe044c 20-Dec-2010 Johannes Carlsson <johannes.carlsson.x@sonyericsson.com> Closing cursor in finalizer to avoid GREF and fd leak in acore

The finalize() call did not clean up completely, this eventually
caused the android.process.acore to crash since it ran out of fds
and GREF to increased above 2000 if an application forgot to close
its cursor objects. A warning was also added when this happens so
that application developers can correct their mistake. The
included test case tries to verify that the finalizer works as
expected by creating a bunch of Cursor objects without closing
them (without this fix the acore process crashes after about 400
iterations and the test case ends with "Process crashed").

Change-Id: I11e485cef1ac02e718b2742108aa88793666c31d
/frameworks/base/core/tests/coretests/src/android/content/ContentResolverTest.java