sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

You could try to get nearer to the point, it fails, if you run your
script from command line with option -s, so at least the logging is
available after the crash.

If you want to watch "the road to hell", you might make some
intermediate regions/matches visible with Region.highlight(1) and/or
watch your script in slow motion while drinking a cup of coffee or what
ever you like.

Since the problem is with awt.dll, I am rather sure it has something to
do with the bug I mentioned already (so currently no solution available
with your system)

** Summary changed:

- X-1.0rc2: Exception access violation
+ X-1.0rc2: Windows: Crash in Java awt.dll

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

Title:
  X-1.0rc2: Windows: Crash in Java awt.dll

Status in Sikuli:
  New

Bug description:
  Sikuli periodically exits with fatal error. The log is attached.