RFR: 8064909: FragmentMetaspace.java got OutOfMemoryError
jon.masamitsu at oracle.com
Wed Nov 26 19:04:49 UTC 2014
Your change makes this test pass but it seems like at
some future date 300m might not be big enough
(for whatever reason). Could the test be make to
caught an OOME, print out a message saying that
an OOME doesn't mean the test failed but that
the test needs a larger heap? Then pass an
exception up (maybe some type of Runtime
exception - sorry if that is vague but I don't
what type of exception would make sense). That
would mean we wouldn't have to spend time
diagnosing what the OOME means again.
On 11/26/2014 5:36 AM, Michail Chernov wrote:
> Please review this simple fix for nightly test failure:
> Problem: test fails because of OOME (not enough heap size).
> Solution: heap size were increased.
More information about the hotspot-gc-dev