Hi Vladimir, Thanks for looking into. This is intermittent crash, and is reproducible in windows debug build environment. Below is the testing performed.
1. Issues observed 7/100 runs, ReservedCodeCacheSize=20m with "-XX:+UnlockExperimentalVMOptions -XX:+EnableJVMCI -XX:+UseJVMCICompiler" 2. Issues observed 0/300 runs, ReservedCodeCacheSize=30m with "-XX:+UnlockExperimentalVMOptions -XX:+EnableJVMCI -XX:+UseJVMCICompiler" Thanks, Fairoz > -----Original Message----- > From: Vladimir Kozlov > Sent: Monday, August 17, 2020 11:22 PM > To: Fairoz Matte <fairoz.ma...@oracle.com>; hotspot-compiler- > d...@openjdk.java.net; serviceability-dev@openjdk.java.net > Cc: Coleen Phillimore <coleen.phillim...@oracle.com>; Dean Long > <dean.l...@oracle.com> > Subject: Re: RFR(s): 8248295: > serviceability/jvmti/CompiledMethodLoad/Zombie.java failure with Graal > > Hi Fairoz, > > How you determine that +10Mb is enough with Graal? > > Thanks, > Vladimir > > On 8/17/20 5:46 AM, Fairoz Matte wrote: > > Hi, > > > > > > > > Please review this small test change to work with Graal. > > > > > > > > Background: > > > > Graal require more code cache compared to c1/c2. but the test case always > set it to 20MB. This may not be sufficient when running graal. > > > > Default configuration for ReservedCodeCacheSize = 250MB > > > > With graal enabled, ReservedCodeCacheSize = 350MB > > > > > > > > Either we can modify the framework to honor ReservedCodeCacheSize for > graal or just update the testcase. > > > > There are not many test cases they rely on ReservedCodeCacheSize or > InitialCodeCacheSize. So the fix prefer the later one. > > > > > > > > JBS - https://bugs.openjdk.java.net/browse/JDK-8248295 > > > > Webrev - http://cr.openjdk.java.net/~fmatte/8248295/webrev.00/ > > > > > > > > Thanks, > > > > Fairoz > > > > > >