RFR: 6744: Upgrading to Eclipse RCP 2020-03

[Jie Kang]

On Wed, 25 Mar 2020 14:34:31 GMT, Jie Kang <jkang at openjdk.org> wrote:

>> Using 2020-03 as default. Removing 2019-09.
>
> Built okay on Linux Fedora 30. However when running jmc against:
> openjdk version "11.0.6" 2020-01-14
> OpenJDK Runtime Environment 18.9 (build 11.0.6+10)
> OpenJDK 64-Bit Server VM 18.9 (build 11.0.6+10, mixed mode, sharing)
> I saw a crash. I had MXBean window of JMC itself and a flight recording window of JMC itself (last 5 minutes).
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x00007f5daa42de54, pid=11529, tid=11547
> #
> # JRE version: OpenJDK Runtime Environment (11.0.6+10) (build 11.0.6+10)
> # Java VM: OpenJDK 64-Bit Server VM (11.0.6+10, mixed mode, sharing, tiered, compressed oops, g1 gc, linux-amd64)
> # Problematic frame:
> # C  [libpthread.so.0+0xfe54]  pthread_getcpuclockid+0x4
> 
> I'm reporting this early here; maybe it's unrelated to updating to 2020-03. I'm going to investigate further, try to
> reproduce and open an issue.

Well I was able to reproduce on jmc with 2020-03 (4 times so far) but not jmc with 2019-12, which strongly suggests
there is a bug introduced here. However, the stack trace is through jfrPeriodic emission of cpu events, which seems
more like an issue from the jvm. Weird. I opened a bug to track this here: https://bugs.openjdk.java.net/browse/JMC-6749

I'll be investigating as time permits; maybe someone else could also take a look.

-------------

PR: https://git.openjdk.java.net/jmc/pull/69