ZSDK_API Crashing JVM


Audience
Tags

After updating the JVM to azul 8.64, the ZSDK_API is now crashing the JVM. hs_err file is attached.

Attachments
Submitted by SSi1 on August 01, 2022 Permalink

The Link-OS SDK for PC-Java (2.14.5198) has not been tested against the azul environment. There might be some incompatibility issues that cause the exception.  

Submitted by Kevin Smotherman on August 03, 2022 Permalink

I tested with the following Zulu Java FX versions:
• 8.52 (8.0.282)
• 8.54 (8.0.292)
• 8.56 (8.0.302)
• 8.62 (8.0.332)
• 8.64 (8.0.342)

From testing all these, 8.52 and 8.54 worked without any crashes, all others did.
You mentioned testing with Oracle 8.0.291 also crashes. This might still be an issue with Zebra as the issue exist with a different vendor.

If we search more into the Visual Studio theory, I found that Oracle moved to VS2017 in version 8.0.261 (https://www.oracle.com/java/technologies/javase/8all-relnotes.html#R180…). I can assume that if you test using Oracle 8.0.261 you will have the same issue, yet if you test the previous (8u251) it will work.
At our end, the VS change occurred with 8.56 (8.0.302) release (https://docs.azul.com/core/zulu-openjdk/release-notes/july-2021#whats-n…) where the Microsoft builds were compiled with VS2017. Note that from my tests, this version and newer we see the crashes, as for the older versions (8.52/8.54) we are using VS2010.

If the issue is with the VS runtime, Zebra will need to look into how and what they are using to compile the DLLs. If VS is not the issue (for example using VS2017 or newer), Zebra will need to look into this as the errors in the logs show the issue within their code.

Submitted by Kevin Smotherman on August 03, 2022 Permalink

I tested with the following Zulu Java FX versions:
• 8.52 (8.0.282)
• 8.54 (8.0.292)
• 8.56 (8.0.302)
• 8.62 (8.0.332)
• 8.64 (8.0.342)

From testing all these, 8.52 and 8.54 worked without any crashes, all others did.
You mentioned testing with Oracle 8.0.291 also crashes. This might still be an issue with Zebra as the issue exist with a different vendor.

If we search more into the Visual Studio theory, I found that Oracle moved to VS2017 in version 8.0.261 (https://www.oracle.com/java/technologies/javase/8all-relnotes.html#R180…). I can assume that if you test using Oracle 8.0.261 you will have the same issue, yet if you test the previous (8u251) it will work.
At our end, the VS change occurred with 8.56 (8.0.302) release (https://docs.azul.com/core/zulu-openjdk/release-notes/july-2021#whats-n…) where the Microsoft builds were compiled with VS2017. Note that from my tests, this version and newer we see the crashes, as for the older versions (8.52/8.54) we are using VS2010.

If the issue is with the VS runtime, Zebra will need to look into how and what they are using to compile the DLLs. If VS is not the issue (for example using VS2017 or newer), Zebra will need to look into this as the errors in the logs show the issue within their code.

Submitted by Kevin Smotherman on August 03, 2022 Permalink

I tested with the following Zulu Java FX versions:
• 8.52 (8.0.282)
• 8.54 (8.0.292)
• 8.56 (8.0.302)
• 8.62 (8.0.332)
• 8.64 (8.0.342)

From testing all these, 8.52 and 8.54 worked without any crashes, all others did.
You mentioned testing with Oracle 8.0.291 also crashes. This might still be an issue with Zebra as the issue exist with a different vendor.

If we search more into the Visual Studio theory, I found that Oracle moved to VS2017 in version 8.0.261 (https://www.oracle.com/java/technologies/javase/8all-relnotes.html#R180…). I can assume that if you test using Oracle 8.0.261 you will have the same issue, yet if you test the previous (8u251) it will work.
At our end, the VS change occurred with 8.56 (8.0.302) release (https://docs.azul.com/core/zulu-openjdk/release-notes/july-2021#whats-n…) where the Microsoft builds were compiled with VS2017. Note that from my tests, this version and newer we see the crashes, as for the older versions (8.52/8.54) we are using VS2010.

If the issue is with the VS runtime, Zebra will need to look into how and what they are using to compile the DLLs. If VS is not the issue (for example using VS2017 or newer), Zebra will need to look into this as the errors in the logs show the issue within their code.

Submitted by Kevin Smotherman on August 03, 2022 Permalink

I tested with the following Zulu Java FX versions:
• 8.52 (8.0.282)
• 8.54 (8.0.292)
• 8.56 (8.0.302)
• 8.62 (8.0.332)
• 8.64 (8.0.342)

From testing all these, 8.52 and 8.54 worked without any crashes, all others did.
You mentioned testing with Oracle 8.0.291 also crashes. This might still be an issue with Zebra as the issue exist with a different vendor.

If we search more into the Visual Studio theory, I found that Oracle moved to VS2017 in version 8.0.261 (https://www.oracle.com/java/technologies/javase/8all-relnotes.html#R180…). I can assume that if you test using Oracle 8.0.261 you will have the same issue, yet if you test the previous (8u251) it will work.
At our end, the VS change occurred with 8.56 (8.0.302) release (https://docs.azul.com/core/zulu-openjdk/release-notes/july-2021#whats-n…) where the Microsoft builds were compiled with VS2017. Note that from my tests, this version and newer we see the crashes, as for the older versions (8.52/8.54) we are using VS2010.

If the issue is with the VS runtime, Zebra will need to look into how and what they are using to compile the DLLs. If VS is not the issue (for example using VS2017 or newer), Zebra will need to look into this as the errors in the logs show the issue within their code.