Question #228550 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/228550
Status: Open => Answered
RaiMan proposed the following answer:
Since I do not know, what you are doing, it might be the other way round:
Because for some reason Sikuli during the run blocks more and more memory, this
slows down you app a bit, which in turn slows down the GUI's turnaround time,
which leads to longer waits in Sikuli, which in turn means more search cycles
and hence more 100% cpu consumption.
Still the question is left: what makes Sikuli to block more and more
memory, if this is so?
--- Each step imports/reloads different modules dynamically
Since you use reloads, I suppose you are constantly working in the IDE.
So before you make a "productive" run, restart the IDE.
--
You received this question notification because you are a member of
Sikuli Drivers, which 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
