X-1.0rc3-931: Java heap space exhausted with long running script using Region.right() .below() .nearby().
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SikuliX |
Fix Committed
|
Critical
|
RaiMan |
Bug Description
******** details - workaround
only Region.right() and .below() and .nearby() are affected.
.above() and .left() are ok.
There is no other workaround, than to make your own functions, to get a Region right or below or nearby of a given region.
-------
It took me a while* to track this one down:
NO memory leak:
def getNumbers(numType, region):
return 0
def test()
x=regions[
getNumbers(
while True:
test()
MEMORY LEAK:
def getNumbers(numType, region):
return 0
def test()
x=regions[
getNumbers(
while True:
test()
System: win7 64bit
JRE 1.6.32 (JRE1.7.04 tested as well)
Sikuli X1.0rc3(905) (1.0RC930 tested as well)
I've tested a few variations of the code above already. I will go on, since that script is essential to a project I am running.
PS: getNumbers is my own text (number) recognition algorithm since region.text() isn't working yet.
* "a while" == 12 days - anyway, sikuli is really good for it's purpose
description: | updated |
Changed in sikuli: | |
status: | New → Confirmed |
summary: |
- Java heap space exhausted with long running script using Region.right() - .below() .nearby(). + X-1.0rc3-931: Java heap space exhausted with long running script using + Region.right() .below() .nearby(). |
Changed in sikuli: | |
status: | Confirmed → In Progress |
assignee: | nobody → RaiMan (raimund-hocke) |
milestone: | none → x1.0 |
status: | In Progress → Fix Committed |
tags: | added: fkt-nearby |
tags: |
added: fkt-region removed: fkt-nearby |
Changed in sikuli: | |
importance: | Undecided → High |
Changed in sikuli: | |
status: | Fix Committed → In Progress |
milestone: | x1.0 → x1.1 |
Changed in sikuli: | |
status: | In Progress → Fix Committed |
Changed in sikuli: | |
importance: | High → Critical |
--- MEMORY LEAK
How did you detect this?
What are the observed effects?