tree 236ef466b1d9286104be42def2cee7d12e525eb2
parent fe7aee2d20b47dad6029a588e0c7394f0c75d080
author Mathieu Chartier <mathieuc@google.com> 1403888232 -0700
committer Mathieu Chartier <mathieuc@google.com> 1403888232 -0700

Don't allow negative GetFreeMemory.

The max allowed footprint is only updated after the GC. But we can
still allocate even if bytes_allocated > max_allowed_footprint_.
This means that we used to be able to get a negative value if
bytes_allocated > max_allowed_footprint_.

External bug:
https://code.google.com/p/android/issues/detail?id=72221

Change-Id: I4ef9a534e29211786e82cdcb2582c11ab37a348a