sikuli-driver team mailing list archive

[RaiMan <question183049@xxxxxxxxxxxxxxxxxxxxx>]

Question #183049 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/183049

    Status: Open => Needs information

RaiMan requested more information:
So it seems that you are only using the Java API functions from a Java
program having sikuli-script.jar somewhere in the java class path.

Then all parameters about java memory management have to be given to the
final java command, that runs the program. Any specifications in any
Sikuli specific area (like the above mentioned info.plist) are not
relevant for your situation.

Both above mentioned -Dsikuli.*** parameters have nothing to do with
Sikuli, must belong to your framework.

Since the heap space is mainly used as a call stack, it might be
interesting, how the Sikuli API is used in your "scripts".

With rc3, there are currently no memory leaks reported, that might help
in your heap space situation.

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.