I am trying to run katalon using console mode commands. I am using powershell remote to execute the commands and getting below error.
!ENTRY org.eclipse.core.resources 2 10035 2018-04-04 16:27:29.035
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
Starting Groovy-Eclipse compiler resolver. Specified compiler level: unspecified
131 2.4.7.xx-201611170128-e46 = ACTIVE
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 1538896 bytes for Chunk::new
# An error report file with more information is saved as:
# C:\Users\xxxxx\hs_err_pid8644.log
# Compiler replay data is saved as:
--------------------------------------------
in the log file it says below solutions:
# Possible solutions:
Reduce memory load on the system
Increase physical memory or swap space
Check if swap backing store is full
Use 64 bit Java on a 64 bit OS
Decrease Java heap size (-Xmx/-Xms)
Decrease number of Java threads
Decrease Java thread stack sizes (-Xss)
Set larger code cache with -XX:ReservedCodeCacheSize=
How can I update -XX:ReservedCodeCacheSize= value. I tired to update the file for jvm.cfg which is in (\Katalon_Studio_Windows_64-5.3.1\jre\lib\amd64\jvm.cfg) , But after that Katalon studio is complaining about the newly added item.
I aslo noticed that Kalaton is using eclipsec.exe , Can we create a config file for that or How can I fix this out of memory issue:
The message above means that you’re running so many programs on your PC that there is no memory left to run one more. This isn’t a Java problem and no Java option is going to change this.
Use the Task Manager of Windows to see how much of your 4GB RAM is actually free. My guess is that somewhere, you have a program that eats all the memory. Find it and kill it.
EDIT You need to understand that there are two types of “out of memory” errors.
The first one is the OutOfMemoryException which you get when Java code is running and the Java heap is not large enough. This means Java code asks the Java runtime for memory. You can fix those with -Xmx…
The other error is when the Java runtime runs out of memory. This isn’t related to the Java heap at all. This is an error when Java asks the OS for more memory and the OS says: “Sorry, I don’t have any.”
To fix the latter, close applications or reboot (to clean up memory fragmentation).