JVMTI OOM handling when arrays / objects are too large
jeremymanson at google.com
Sat Jun 6 09:38:29 PDT 2009
Martin Buchholz tells me that three things have to happen to get a patch in:
1) Someone inside Sun has to file a bug. Usually, this seems to be in
the other bug database, but I guess it doesn't matter?
2) Two OpenJDK members have to review it (in practice).
Is my understanding correct?
On Fri, Jun 5, 2009 at 4:31 PM, Tim Bell <Tim.Bell at sun.com> wrote:
> Hi Jeremy
>> I was talking to some of the HS team at JavaOne, and they encouraged
>> me to send some of the patches that we are working on at Google back
>> to Sun. (Everyone at Google is covered under a blanket SCA, so we can
>> contribute back anything done by any Googler).
>> To get started and test the waters, and because I have never tried to
>> contribute to OpenJDK before, I thought I would send on a
>> nearly-trivial fix that I made last year in response to a user
>> complaint. The issue was that when the user specifies
>> -XX:OnOutOfMemoryError, and the OOM is thrown because a single memory
>> allocation was too close to Integer.MAX_VALUE, the OnOutOfMemoryError
>> command would not be executed. I've attached the patch. Let me know
>> what I should do to proceed.
> I created a bugzilla report for this issue:
> That way we won't lose it in a pile of email.
More information about the hotspot-runtime-dev