JVMTI OOM handling when arrays / objects are too large
jeremymanson at google.com
Tue Jun 23 14:32:21 PDT 2009
So, it should have the JVMTI_RESOURCE_EXHAUSTED_OOM_ERROR but not the
JVMTI_RESOURCE_EXHAUSTED_JAVA_HEAP? I can change that.
On Tue, Jun 23, 2009 at 12:45 PM, Alan Bateman<Alan.Bateman at sun.com> wrote:
> Jeremy Manson wrote:
>> On Wed, Jun 17, 2009 at 3:13 AM, Alan Bateman<Alan.Bateman at sun.com> wrote:
>>> Hopefully this helps. I can review the patch but as I'm not working in
>>> area on a daily basis, so it would be best to have a reviewer from the
>>> hotspot team (and I assume you'll need someone to push this through
>> So, does anyone want to step up and review it? I know several of you
>> have already looked at it.
> Is there is an updated webrev? In my last year I had hoped we wouldn't send
> the JVM TI ResourceExhausted event because this isn't really a resource
> exhaustion case.
More information about the hotspot-runtime-dev