Question #691654 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/691654
RaiMan proposed the following answer: Maybe this is a workaround helper for you: - start the IDE normally and run your script in the IDE - in $JAVA_HOME/bin there is a command jcmd - in parallel to the running script run it in a terminal as $JAVA_HOME/bin/jcmd without any parameters and you will get the active JVMs - find the pid for the JVM running org.sikuli.ide.SikulixIDE - from time to time in the same terminal window run jcmd <IDE-PID> GC.run This should run a garbage collection and the memory usage should be at a lower level afterwards. I will use this utility to make my tests. -- You received this question notification because your team Sikuli Drivers is an answer contact for Sikuli. _______________________________________________ Mailing list: https://launchpad.net/~sikuli-driver Post to : [email protected] Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
