RFR 8207364: nsk/jvmti/ResourceExhausted/resexhausted003 fails to start
Chris Plummer
chris.plummer at oracle.com
Thu Jul 26 04:09:14 UTC 2018
Hi Daniil,
After reading some old comments I added to JDK-6606767, I wonder if
bumping the metaspace size all the way up to 16m is the right thing to
do. It seems the test wants to exhaust the metaspace, so maybe it should
be set it to the smallest allowed size. Is the test still exhausting the
metaspace even when it is 16M. Is there a smaller size that will also work?
Also, regarding the class path, what impact was this bug having on the test?
thanks,
Chris
On 7/25/18 4:32 PM, serguei.spitsyn at oracle.com wrote:
> Hi Daniil,
>
> It looks good to me.
> What is the need to increase the metaspace size?
>
> Thanks,
> Serguei
>
>
> On 7/25/18 16:11, Daniil Titov wrote:
>> Hello,
>>
>> Please review the change that fix the test issue. The fix increases
>> the metaspace size and corrects the path to the class files.
>>
>> Webrev: http://cr.openjdk.java.net/~dtitov/8207364/webrev.01/
>> Issue: https://bugs.openjdk.java.net/browse/JDK-8207364
>>
>> Thanks!
>>
>> Best regards,
>> Daniil
>>
>>
>>
>
More information about the serviceability-dev
mailing list