RFR: 8230454: [Graal] Add "com/sun/crypto/provider/KeyFactory/TestProviderLeak.java" to Graal problem list.

[dean.long at oracle.com]

On 9/8/19 7:51 PM, Xiaohong Gong (Arm Technology China) wrote:
>
> > I was going to suggest increasing the heap size, but that won't 
> necessarily help because the JVMCI compiler gets started lazily and 
> the app could still have used up all of memory by that time.? I'm 
> skeptical of the value of running this with Graal anyway, so I'm OK 
> with this change.
>
> > dl
>
> Hi Dean,
>
>   Thanks for reviewing! So does it also need to be reviewed by someone 
> else?
>

No, it looks trivial, so one reviewer should be enough.

dl

> Thanks,
>
> Xiaohong Gong
>
> *From:* Xiaohong Gong (Arm Technology China)
> *Sent:* Thursday, September 5, 2019 10:51 AM
> *To:* hotspot-compiler-dev at openjdk.java.net; graal-dev at openjdk.java.net
> *Cc:* nd <nd at arm.com>
> *Subject:* RFR: 8230454: [Graal] Add 
> "com/sun/crypto/provider/KeyFactory/TestProviderLeak.java" to Graal 
> problem list.
>
> Hi,
>
>   Please help to review this small patch:
>
>   Webrev: http://cr.openjdk.java.net/~xgong/rfr/8230454/webrev.00/
>
>   JBS: https://bugs.openjdk.java.net/browse/JDK-8230454 
> <https://bugs.openjdk.java.net/browse/JDK-8230454>
>
>   Jtreg test 
>  "com/sun/crypto/provider/KeyFactory/TestProviderLeak.java" unstably 
> fails with graal
>
> by throwing the OOME during JVMCI compiler initialization.
>
>   It is caused by setting "-Xmx20m" for the application, which makes 
> the java heap not enough for
>
> the VM. A simple fix is to add it to the graal problem list. Hope it's 
> ok for libgraal, so that we can
>
> move it out from the list once libgraal is enabled.
>
> Thanks,
>
> Xiaohong Gong
>