Knime 5.5 Chromium Crashing

[Sarah_rushton]

Hello,

We use knime for a number of scheduled workflows from ETL’s to report automation. This has worked perfectly, running multiple workflows at the same time on the same workspace via .bat files. However, we ungraded to Knime 5.5 and suddenly our workflows stopped running due to the below error:

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

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ff8653dac8f, pid=5172, tid=13952

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)

Problematic frame:

C [libcef.dll+0x468ac8f]

It looks like something relating to chromium/OpenJDK is being locked meaning other workflows can’t run. This has never been a problem before 5.5, and we don’t know how to fix this?

Any help is much appreciated

Thanks

[ScottF]

Hi @Sarah_rushton and welcome to the forum.

I see you also posted this is the 5.5 Release thread. Did you see Martin’s reply there already?

Out now: KNIME Analytics Platform 5.5

Hi @Sarah_rushton, hi @jmartinsonhr23, as @leo_woerteler already remarked, it’s most likely due to the ‘embedded browser’ (CEF). We initialize CEF on start-up which helps to prevent problems when CEF is initialized on demand later and memory is tight. But you can turn that off by setting the system property -Dorg.knime.js.cef.skip_windowless_chromium_initialization=true. Maybe that helps as workaround (provided you don’t use view-image-generation or report-generation - which needs CEF and will …

While we’re working on a fix, since you’re already relying on KNIME for your scheduled workflows - have you considered our Team Plan? There’s a free trial available.