A fatal error has been detected by the Java Runtime Environment in 5.4.0

KNIME Analytics Platform
1

Hi,
We are trying to trigger a KNIME workflow from an Excel based application using a batch file. But the action to trigger the workflow is getting failed and we are getting the following error from the log file:

A fatal error has been detected by the Java Runtime Environment:

Internal Error (os_windows_x86.cpp:143), pid=11228, tid=1632

guarantee(result == EXCEPTION_CONTINUE_EXECUTION) failed: Unexpected result from topLevelExceptionFilter

JRE version: OpenJDK Runtime Environment Temurin-17.0.5+8 (17.0.5+8) (build 17.0.5+8)

Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.5+8 (17.0.5+8, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)

Core dump will be written. Default location: C:\SOP Platform\WebServices\VERTIV_DEMO\hs_err_pid11228.mdmp

If you would like to submit a bug report, please visit:

GitHub Ā· Where software is built

The crash happened outside the Java Virtual Machine in native code.

See problematic frame for where to report the bug.

--------------- S U M M A R Y ------------

Command Line: -Djava.security.properties=plugins/org.knime.binary.jre.win32.x86_64_17.0.5.20221116/security.properties -Dorg.apache.cxf.bus.factory=org.knime.cxf.core.fragment.KNIMECXFBusFactory -Dorg.apache.cxf.transport.http.forceURLConnection=true -server -Dsun.java2d.d3d=false -Dosgi.classloader.lock=classname -XX:+UnlockDiagnosticVMOptions -Dsun.net.client.defaultReadTimeout=0 -Dknime.xml.disable_external_entities=true -Dcomm.disable_dynamic_service=true -Dp2.trustedAuthorities=https://update.knime.com -Declipse.e4.inject.javax.warning=false -Dorg.eclipse.ecf.provider.filetransfer.excludeContributors=org.eclipse.ecf.provider.filetransfer.httpclientjava --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/java.nio.channels=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.base/sun.nio=ALL-UNNAMED --add-opens=java.desktop/javax.swing.plaf.basic=ALL-UNNAMED --add-opens=java.base/sun.net.www.protocol.http=ALL-UNNAMED --add-opens=java.base/sun.net.www.protocol.https=ALL-UNNAMED --add-opens=java.base/java.util.regex=ALL-UNNAMED -Xmx8191m -Dorg.eclipse.swt.browser.IEVersion=11001 -Dsun.awt.noerasebackground=true -Dequinox.statechange.timeout=30000 -Djdk.httpclient.allowRestrictedHeaders=content-length -Darrow.enable_unsafe_memory_access=true -Darrow.memory.debug.allocator=false -Darrow.enable_null_check_for_get=false --add-opens=java.security.jgss/sun.security.jgss.krb5=ALL-UNNAMED --add-exports=java.security.jgss/sun.security.jgss=ALL-UNNAMED --add-exports=java.security.jgss/sun.security.jgss.spi=ALL-UNNAMED --add-exports=java.security.jgss/sun.security.krb5.internal=ALL-UNNAMED --add-exports=java.security.jgss/sun.security.krb5=ALL-UNNAMED

Note: This same action is triggering the KNIME workflow(Just one excel read and write node) and getting completed successfully for KNIME version till 5.4.0

2

Hi @a_vishnu,

is there some hs_err*.log somewhere?

See problematic frame for where to report the bug.

Could you look through the log for this ā€œproblematic frameā€ and post it here? Or just post the rest of the error log (knime.log or console content) that you see. Unfortunately, the JVM internal error and the command line are not much to start investigating from.

2 Likes
3

Hi,

PFA

hs_err_pid11228.log (68.6 KB)

4

Thank you for attaching the log file. It looks like there has been some problem while initializing the headless browser (used for image and report generation in the batch application).

Based on the Chromium/CEF version in the log, it seems you are using an older version of KNIME.

Could you test with the zip archive of KNIME 5.4, whether it can reliably run with the batch application? The 5.4 release contains a newer version of Chromium/CEF that might have fixed the problem.

1 Like
5

Hi,

We have tested with 5.4.0, 5.4.1 and 5.4.2 version of KNIME.

ā€˜Based on the Chromium/CEF version in the log, it seems you are using an older version of KNIMEā€™ - The log file that Iā€™ve shared I not sure for which version of KNIME that is, but it must belong to one of the above.

Just to make sure Iā€™ve tried re-installed the 5.4.2 again and Iā€™m getting the same error.
hs_err_pid10124.log (68.4 KB)

This new 5.4.2 version Iā€™ve installed using the windows installer, do you think the zip archive method would have different Chromium/CEF version? is that why you want me to try that?

6

I was suggesting the ZIP version simply because it does not mess with any installed version you may rely on. So itā€™s less intrusive to test something quickly. It has the exact same software, but does not ā€œinstall itselfā€ like the installer-based version.

Iā€™ve forwarded the new log file to the team and will keep you updated if we find out more.

2 Likes
7

I was told adding this parameter to the knime.ini would delay the initialization of CEF: -Dorg.knime.js.cef.skip_windowless_chromium_initialization=true

Could you try it?

1 Like