sikuli-driver team mailing list archive

Thread
Date

Re: [Question #255315]: [sikuli api]finder.find seems memory leak

To: sikuli-driver@xxxxxxxxxxxxxxxxxxx
From: RaiMan <question255315@xxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 07 Oct 2014 08:56:35 -0000
Reply-to: question255315@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

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

    Status: Open => Answered

RaiMan proposed the following answer:
Ok, thanks for testing.
I have to check the percentage calculation (this in fact is only a doc value and not used for anything)

What it shows: the cache is limited to the given about 64 MB, since in the end, with 51 used image files, only 31 are cached.
So at least the cache now is working correctly, in that it does not grow beyond the given max limit.

If 64 MB is too much for you, you can use a lower value or even 0, to switch off caching completely:
Settings.setImageCache(n)

where n is an integer value giving the size in MB or 0 to switch off
caching at any time (which instantly clears the cache too.

The cache size should never exceed n * 1024 KB (which it seems not to
do).

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