[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-core-libs-dev
Subject:    Re: [12] 8206403: ByteArrayOutputStream hugeCapacity method can return invalid capacity
From:       Brian Burkhalter <brian.burkhalter () oracle ! com>
Date:       2018-07-24 16:46:48
Message-ID: 24EECC36-157E-424C-BCB2-41A7B9BC5151 () oracle ! com
[Download RAW message or body]

Hi Roger,

I tend to agree with you. Also, I think that if MAX_ARRAY_SIZE were to be dealt with \
it should be so globally for consistency and not just in this one class.

Thanks for the follow up and the historical link (context).

Brian

On Jul 24, 2018, at 8:37 AM, Roger Riggs <roger.riggs@oracle.com> wrote:

> A followup on the issues raised by Martin.
> 
> The original issue[1] was that the resize by doubling approach failed to take \
> advantage of nearly 1G of potential buffer space.
> The new issue is raised against getting the last additional 2-6 bytes of buffer \
> space before the hitting the VM's implementation limit.
> 
> I don't think its worth the effort to try to ensure those last few bytes are \
> available before throwing OOM. Reconsidering, I would close the issue as WillNotFix \
> for the reason that the application is encountering an implementation limit.
> 
> Regards, Roger
> 
> [1] https://bugs.openjdk.java.net/browse/JDK-8055949


[prev in list] [next in list] [prev in thread] [next in thread]