Unable to open a huge workflow already executed

I’m currently facing a problem in opening a huge workflow that has already been successfully executed on Ubuntu machine with 4 core and 12gb of RAM.

After that the Ubuntu machine resources have been reduced to just 1 core and 2gb of RAM, and unfortunately I’m not able to open the workflow again. Knime always crashes with this error:

JVM terminated. Exit code=1
/home/ubuntu/knime_3.3.1//plugins/org.knime.binary.jre.linux.x86_64_1.8.0.152-01/jre/bin/java
-server
-Dsun.java2d.d3d=false
-Dosgi.classloader.lock=classname
-XX:+UnlockDiagnosticVMOptions
-XX:+UnsyncloadClass
-Dsun.net.client.defaultReadTimeout=0
-XX:CompileCommand=exclude,javax/swing/text/GlyphView,getBreakSpot
-Xmx2048m
-Dorg.eclipse.swt.internal.gtk.disablePrinting
-jar /home/ubuntu/knime_3.3.1//plugins/org.eclipse.equinox.launcher_1.3.200.v20160318-1642.jar
-os linux
-ws gtk
-arch x86_64
-showsplash
-launcher /home/ubuntu/knime_3.3.1/knime
-name Knime
–launcher.library /home/ubuntu/knime_3.3.1//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.400.v20160518-1444/eclipse_1617.so
-startup /home/ubuntu/knime_3.3.1//plugins/org.eclipse.equinox.launcher_1.3.200.v20160318-1642.jar
–launcher.overrideVmargs
-exitdata 308005
-vm /home/ubuntu/knime_3.3.1//plugins/org.knime.binary.jre.linux.x86_64_1.8.0.152-01/jre/bin/java
-vmargs
-server
-Dsun.java2d.d3d=false
-Dosgi.classloader.lock=classname
-XX:+UnlockDiagnosticVMOptions
-XX:+UnsyncloadClass
-Dsun.net.client.defaultReadTimeout=0
-XX:CompileCommand=exclude,javax/swing/text/GlyphView,getBreakSpot
-Xmx2048m
-Dorg.eclipse.swt.internal.gtk.disablePrinting
-jar /home/ubuntu/knime_3.3.1//plugins/org.eclipse.equinox.launcher_1.3.200.v20160318-1642.jar

I have already changed the knime.ini file with my current low resources configuration.
I have also attached the complete knime error_log file as zip file, in which it says that there is insufficient memory for the Java Runtime Environment to continue. Native memory allocation (mmap) failed to map 536670208 bytes for committing reserved memory.

How could I solve it? And, second question, is there a way to at least just open it? Since it’s already executed and I would like to just take a look to each operation node already executed.

hs_err_pid16309.log.zip (21.5 KB)

If you only have 2GB of RAM you cannot allocate all of it to KNIME. You have to lower the -Xmx value in your knime.ini to at most 60% (±) of the available RAM.

Hi thor,
I have already reduced to -Xmx1024m in knime.ini, but knime stil crashes when I’m trying to open that workflow.

Then there simply isn’t enough memory in your system. Try lowering it further. KNIME should run more or less fine with 512MB.

Thank you thor for the suggestion.
Finally with 512m I’m able to open it, and everything went fine.

~G

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.