Comment 3 for bug 1013396

Ok, but this is not a memory leak caused by a specific Sikuli feature, this is some strange behavior of the Java GC (garbage collection), while running a Sikuli script.

The effect of increase of minimum memory consumption is more substantial, when running a script in the IDE compared to running it from command line.

Running a script in IDE directly after IDE start, the base memory consumption jumps from about 120 MB to about 250 MB after having initialized the Sikuli basics and started running the script.

Then memory consumption rises to a value of about base+350MB, before falling back to base (because of GC). The problem is, that base is constantly increasing with each fallback (IDE: +10-30MB, command line using sikuli-script.jar: +0-5MB varying).

So in my opinion, this is a general IDE-script-run problem.

See what happens if you run your script from command line using:
java -jar path-to-sikuli-script.jar path-to-script.sikuli