| 1a9cff8f68deffd618c5cba1f22f0fb0e396e067 |
|
17-Nov-2011 |
Jesse Wilson <jessewilson@google.com> |
Always trigger finalization the same way in our tests.
This came up when I was recently writing a ZipFile finalization test
and I needed to copy-paste the finalizer recipe.
Change-Id: Ia67061b3dba1a7011c93c9a81e2a963876b238a1
|
| 2ae03aff183962fd52a0465f60db86fa16e49c4d |
|
27-Oct-2010 |
Jesse Wilson <jessewilson@google.com> |
Fixing concurrency bug in CloseGuardTester.
Hudson was complaining with this exception:
java.util.ConcurrentModificationException
at java.util.ArrayList$ArrayListIterator.next(ArrayList.java:576)
at libcore.dalvik.system.CloseGuardTester.assertEverythingWasClosed(CloseGuardTester.java:59)
at libcore.java.lang.ProcessBuilderTest.testDestroyDoesNotLeak(ProcessBuilderTest.java:91)
Change-Id: Ie6be12186c94e14ba4d5df8a392144269abb598b
|
| 2353846b64570fa5932028143a0af507d41a85c5 |
|
25-Oct-2010 |
Jesse Wilson <jessewilson@google.com> |
Close process-spawned streams when the process is destroyed.
This is consistent with the RI's behavior. I can't come up with
a reasonable approach to closing these streams if they are never
requested; that's presumably a finalizer problem anyway because
only the finalizer knows that the streams won't be needed.
This change also adds test infrastructure around CloseGuard.
My approach hooks into the logger rather than reflection because
I can't be sure where the CloseGuard instance would be in the
object hierarchy. This approach also degrades reasonably when
run on the reference implementation (where it passes).
Change-Id: I08e882494d69d4245e40fb1035edbc6d3df23fbc
http://b/3111120
|