Quarkus CLI crashes JVM when running on Windows in dev mode with gradle project

[rsvoboda]

Describe the bug

Quarkus CLI crashes JVM when running on Windows in dev mode with gradle project

Experienced with Quarkus 3.1.2.Final and Quarkus main.

Running gradlew quarkusDev works fine. Running quarkus dev end with JVM crash - see hs_err_pid1132.log.

I'm using https://community.chocolatey.org/packages/Temurin17 (17.0.7) and https://community.chocolatey.org/packages/quarkus (3.1.2.Final)

The failure was also reproduced by @brunobat

Expected behavior

No JVM crash

Actual behavior

Quarkus CLI crashes JVM when running on Windows in dev mode with gradle project

How to Reproduce?

• Run Windows machine
• Install quarkus CLI
• Get app from https://code.quarkus.io/?b=GRADLE
• Unzip the app and navigate to the directory
• run quarkus dev
• JDV crashes

Running gradlew quarkusDev works.

Output of uname -a or ver

Windows 10

Output of java -version

Java 17

GraalVM version (if different from Java)

No response

Quarkus version or git rev

3.1.2.Final

Build tool (ie. output of mvnw --version or gradlew --version)

gradlew from the code.quarkus app

Additional information

No response

[quarkus-bot]

/cc @ebullient (cli), @glefloch, @maxandersen (cli), @quarkusio/devtools

[dresch86]

Are there any updates on this? I am still seeing the same behavior.

[maxandersen]

Could this be caused by fusesource/jansi#66 ?

Basically two different versions being loaded?

[rsvoboda]

I'm not sure if the linked issue is the problem, could be related though. This issue is Windows specific, wasn't hit on other operating system. Linked issue is not Windows specific.

dev mode works fine when invoked through gradlew. Quarkus CLI pulls in something problematic, but jansi is not dependency of devtools/cli and unzip -l quarkus-cli-3.10.1-runner.jar| grep -i jansi also didn't give anything.

I tried to force 1.18 using

configurations.all {
  resolutionStrategy {
    force 'org.fusesource.jansi:jansi:1.18'
  }
}

But I got this:

quarkus dev
...
Caused by: java.lang.NoSuchMethodError: 'org.fusesource.jansi.AnsiPrintStream org.fusesource.jansi.AnsiConsole.out()'
        at org.aesh.readline.terminal.impl.WinSysTerminal.<init>(WinSysTerminal.java:44)
        at org.aesh.readline.terminal.impl.WinSysTerminal.<init>(WinSysTerminal.java:40)
        at org.aesh.readline.terminal.TerminalBuilder.createWindowsTerminal(TerminalBuilder.java:148)
        at org.aesh.readline.terminal.TerminalBuilder.build(TerminalBuilder.java:117)
        at org.aesh.readline.tty.terminal.TerminalConnection.<init>(TerminalConnection.java:91)
        at org.aesh.readline.tty.terminal.TerminalConnection.<init>(TerminalConnection.java:108)
        at io.quarkus.deployment.console.ConsoleHelper.installConsole(ConsoleHelper.java:37)
        at io.quarkus.deployment.console.ConsoleProcessor.setupConsole(ConsoleProcessor.java:79)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:568)
        at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:849)
        at io.quarkus.builder.BuildContext.run(BuildContext.java:256)
        at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
        at org.jboss.threads.EnhancedQueueExecutor$Task.doRunWith(EnhancedQueueExecutor.java:2516)
        at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2495)
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1495)
        at java.base/java.lang.Thread.run(Thread.java:833)
        at org.jboss.threads.JBossThread.run(JBossThread.java:483)

Interestingly, when running gradlew quarkusDev on the same project (forcing org.fusesource.jansi:jansi:1.18) I don't get any compilation errors and dev mode is started. This is super strange to me :/

[FrodoOf9Fingers]

Also experiencing this issue, for the longest time thought it was a disconnect between my IDE and Quarkus. I can confirm that running quarkusDev directly via gradlew bypasses the issue.