New Early Access builds

[Christian Stein]

Hi again!

Another issue I observe with the new Loom EA build is
related to JShell on Windows 10.

The following worky by using the normal 16-ea build:

  java --version
  openjdk 16-ea 2021-03-16
  OpenJDK Runtime Environment (build 16-ea+26-1764)
  OpenJDK 64-Bit Server VM (build 16-ea+26-1764, mixed mode, sharing)

  jshell https://bit.ly/bach-main-boot

Bach boots and a standard "jshell>" prompt appears.

Using 16-loom+9, an EOFException is raised:

  java --version
  openjdk 16-loom 2021-03-16
  OpenJDK Runtime Environment (build 16-loom+9-316)
  OpenJDK 64-Bit Server VM (build 16-loom+9-316, mixed mode, sharing)

  jshell https://bit.ly/bach-main-boot

java.io.EOFException
        at
java.base/java.io.DataInputStream.readInt(DataInputStream.java:398)
        at
java.base/java.io.ObjectInputStream$BlockDataInputStream.readInt(ObjectInputStream.java:3453)
        at
java.base/java.io.ObjectInputStream.readInt(ObjectInputStream.java:1136)
        at
jdk.jshell/jdk.jshell.execution.StreamingExecutionControl.readAndReportExecutionResult(StreamingExecutionControl.java:277)
        at
jdk.jshell/jdk.jshell.execution.StreamingExecutionControl.invoke(StreamingExecutionControl.java:99)
        at
jdk.jshell/jdk.jshell.execution.JdiDefaultExecutionControl.invoke(JdiDefaultExecutionControl.java:160)
        at jdk.jshell/jdk.jshell.Eval.declare(Eval.java:943)
        at jdk.jshell/jdk.jshell.Eval.eval(Eval.java:139)
        at jdk.jshell/jdk.jshell.JShell.eval(JShell.java:493)
        at
jdk.jshell/jdk.internal.jshell.tool.JShellTool.processSource(JShellTool.java:3609)
        at
jdk.jshell/jdk.internal.jshell.tool.JShellTool.processSourceCatchingReset(JShellTool.java:1330)
        at
jdk.jshell/jdk.internal.jshell.tool.JShellTool.processInput(JShellTool.java:1228)
        at
jdk.jshell/jdk.internal.jshell.tool.JShellTool.run(JShellTool.java:1201)
        at
jdk.jshell/jdk.internal.jshell.tool.JShellTool.runFile(JShellTool.java:3090)
        at
jdk.jshell/jdk.internal.jshell.tool.JShellTool.start(JShellTool.java:952)
        at
jdk.jshell/jdk.internal.jshell.tool.JShellToolBuilder.start(JShellToolBuilder.java:254)
        at
jdk.jshell/jdk.internal.jshell.tool.JShellToolProvider.main(JShellToolProvider.java:120)
State engine terminated.

->

Does it make sense to notify kulla-dev about this?


On Tue, Dec 1, 2020 at 10:16 AM Alan Bateman <Alan.Bateman at oracle.com>
wrote:

>
> The builds at the Project Loom Early Access page [1] have been
> refreshed. The latest builds are based on jdk-16+25 (JDK 16 build 25).
>
> There are important stability fixes in this build. We think this build
> should resolve most of the crashes that people have reported over the
> last few months when running with concurrent GCs. We are mostly testing
> with G1 and ZGC.  There may be a small performance impact in some cases
> with the changes but for now, it will be great if you have been seeing
> issues to re-test to see if there are any other issues.
>
> One area that is currently not stable is the debugger support. We are
> mid way through a big re-implementation. The "new approach" upgrades JVM
> TI to fully support virtual threads so that the suspend/resume policies
> needed when debugging can be supported. It also avoids the thread
> identity issues that plagued the original approach. We hope to be at the
> point soon where we can engage with the IDE/debugger maintainers about
> adding support for virtual threads. We expect debuggers will need modest
> changes, esp. in areas where a debugger wants to track all threads or
> enumerate all threads or thread groups.
>
> -Alan
>
> [1] http://jdk.java.net/loom/
>