← Back to team overview

sikuli-driver team mailing list archive

[Bug 887242] Re: Sikuli becomes unreliable after running for a long time

 

OK, success:

10000 times in 580 minutes (nearly 6 hours)

no problems.

If memory would be a problem, you would get a Java exception regarding
memory, but not a FindFailed exception.

Until more information is available, I  reset this bug to a lower level.

** Changed in: sikuli
       Status: New => Opinion

** Summary changed:

- Sikuli becomes unreliable after running for a long time
+ X-1.0rc3: May Be: Sikuli becomes unreliable after running for a long time

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/887242

Title:
  X-1.0rc3: May Be: Sikuli becomes unreliable after running for a long
  time

Status in Sikuli:
  Opinion

Bug description:
  I've been using sikuli recently to automate tasks that are impractical
  for a human to do and I've begun encountering issues in any script
  that runs for more than a couple of hours.

  For example, I have a script which is essentially just locating a
  button and clicking on it, locating it again and clicking on it, etc.
  for a given number of loops.  It works fine for a while, and then
  after about 500 loops (running for over 2 hours) Sikuli stops being
  able to locate the image and flops into it's exception state on every
  subsequent loop.  This is bad.

  I've been able to repro this on mac and windows.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/887242/+subscriptions


References