Quarkus devmode crashes on JDK >= 22 (Windows) #39575
Labels
Milestone
Comments
|
hs_err_pid39660.log: |
|
I tried the same app on Ubuntu and it works just fine, so this issue relates to Windows only I believe. |
Eng-Fouad
changed the title
|
Workaround for this issue on Windows:
|
|
It looks like this native method fails to execute:
|
|
🙏🏼 |
|
Also, just as an fyi, jansi should never be loaded on a non-windows OS. It's only used to convert ansi to windows specific terminal codes and back. |
maxandersen
changed the title
|
This line: Class.forName(CLibrary.class.getName()); // calling static block which calls the private native method CLibrary.init()works fine if we run quarkus in prod mode:
However, it crashes when running in dev mode:
|
|
@Eng-Fouad Is this reproducible with the Adoptium release as well? Could you try that out and if it's still reproducible try to reproduce again with a debugimage so that we can get more info out of the traces? If this is only happening on the Oracle release then you should probably open an issue with them as well. |
Yes, it is reproducible with Adoptium release: build.gradle.kts: Output:
How to reproduce with a debugimage? |
|
Hi @Eng-Fouad
You'll need to download the debug symbols that correspond to the build you are using (for Temurin 22+36, you can get them here) and then unzip the corresponding symbols ( This way you should see method names instead of just offsets (i.e. "[jvm.dll+0x459c68]") in the native frames reported in the hs_err. |
|
Output: hs_err_pid1424.log: Edit: @zakkak wrapped the log in |
|
FWIW, the problematic frames looks very much like those reported in this issue reported with jansi: fusesource/jansi-native#17, although it involves both a different JVM and different OS. EDIT: Also maybe this one: fusesource/jansi#66 ? |
|
I think I found the cause for this issue. According to this page:
I can confirm that setting |
This comment was marked as resolved.
This comment was marked as resolved.
|
Interesting information! I don't much of anything about terminals, so maybe @stuartwdouglas can weigh in here. |
|
As I mentioned in another reply is that the jansi library will only be
called on windows. Ideally this will be fixed in jansi, but adding this
check should also work.
…On Thu, Mar 28, 2024, 16:59 Georgios Andrianakis ***@***.***> wrote:
Interesting information!
I don't much of anything about terminals, so maybe @stuartwdouglas
<https://github.com/stuartwdouglas> can weigh in here.
—
Reply to this email directly, view it on GitHub
<#39575 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAME5BMGTM2YXZM2KNSHX3Y2QV45AVCNFSM6AAAAABE6ROKDSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRVGU3DKMRTHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
🙏🏼 |
|
It seems the fix won't be included in the release 3.11 as well :) |
Eng-Fouad
changed the title
Eng-Fouad
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Simple Quarkus app crashes on Windows using JDK22:
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
Reproducer: https://github.com/Eng-Fouad/quarkus-3.9.0.RC2-with-JDK22
Output of
uname -aorverWindows 11
Output of
java -version22
Quarkus version or git rev
3.9.0.CR2
Build tool (ie. output of
mvnw --versionorgradlew --version)gradle-8.7-rc-3
Additional information
No response
The text was updated successfully, but these errors were encountered: