Question #691654 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/691654
Status: Answered => Solved
Javier Gonzales Rodriguez confirmed that the question is solved:
Thanks RaiMan, that solved my question.
--
You received this question notification because your team Sikuli
Question #691654 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/691654
Status: Open => Answered
RaiMan proposed the following answer:
Thanks for feedback.
The issue is now tracked here:
https://github.com/RaiMan/SikuliX1/issues/323
... so you can close this question.
--
Question #691654 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/691654
Status: Answered => Open
Javier Gonzales Rodriguez is still having a problem:
Hi Raiman,
Again, thanks for the info, it seems like both options (I tested both
for days) are helping to reduce the RAM
Question #691654 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/691654
RaiMan proposed the following answer:
... or you might trigger the garbage collection directly inside the
script:
import java.lang.System as JSYS # at beginning of main script
JSYS.gc() # at loop start or
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
Question #691654 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/691654
Summary changed to:
[2.0.4] possible memory leak with long running scripts
--
You received this question notification because your team Sikuli Drivers
is an answer contact for Sikuli.
6 matches
Mail list logo