tree afeb8a0b82a19dc36d9a36d2c62c863aa2cd89bc
parent 0240d2ba620e42d68fa9b6a6ca4ff01a0c79b8e3
author Lokesh Gidra <lokeshgidra@google.com> 1586928746 -0700
committer Lokesh Gidra <lokeshgidra@google.com> 1588017378 +0000

Handle OOM situation in java-heap more aggressively

Currently we perform several rounds of GCs before throwing out-of-memory
exception. Furthermore, even if a small amount of memory is reclaimed,
we call it success. This leads to janky app behavior and timeouts
during finalization.
In this change we perform the next GC type, and if that doesn't reclaim a
minimum amount of free space, then perform a final GC cycle, which is
full-heap, including soft-references and evacuates all regions to be
thorough. If that also failes, then we throw OOME.

Bug: 144525957
Test: art/test/testrunner/testrunner.py
Change-Id: I34af2250661f886c8c2ba32637ee37886e2021d7