sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

I just googled a bit and found a starting point: when using
OpenCV::IplImage, the data size (whatever that means here) cannot be
more than 2GB. In cases, where the image is too large, one gets the
above exception.

Using cv::Mat as image store does not have this restriction.

Looking into Sikuli's native stuff, in fact in finder.cpp IplImage is
used, but this is code, that is only used together with the text-finding
feature.

Normal find(image) is completly on using cv::Mat, so should not make
this problems.

So the good question is: are you using the text feature?

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

Title:
  [1.0.1] Insufficient Memory in OpenCV after 8 hour script operation

Status in Sikuli:
  In Progress

Bug description:
  I have a script that sometimes hits the following error:

  OpenCV Error: Insufficient memory (Failed to allocate 5714572 bytes) in unknown function, file ..\..\..\..\ocv\opencv\src\cxcore\cxalloc.cpp, line 52
  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  EXCEPTION_UNCAUGHT_CXX_EXCEPTION (0xe06d7363) at pc=0x766bc41f, pid=6940, tid=5460
  #
  # JRE version: 7.0_25-b17
  # Java VM: Java HotSpot(TM) Client VM (23.25-b01 mixed mode, sharing windows-x86 )
  # Problematic frame:
  # C  [KERNELBASE.dll+0xc41f]  RaiseException+0x58
  #
  # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
  #
  # An error report file with more information is saved as:
  # D:\Misc\Scripts\FantaScripts.sikuli\hs_err_pid6940.log
  #
  # If you would like to submit a bug report, please visit:
  #   http://bugreport.sun.com/bugreport/crash.jsp
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.

  I run the script daily.  It can happen very soon after the script
  starts (this morning it too 15 min).  But usually the script runs for
  8+ hours no problem.  This may be a problem with garbage collection;
  but jython leaves that up to Java.  So I am not certain about how I
  could improve the garbage collection.

  OS:
  Win 7 x64

  Sikuli X ver:
  1.0rc3 (r905)

  PyDev ver:
  2.8.2.2013090511

  Eclipse Ver
  Eclipse Standard/SDK

  Version: Kepler Release
  Build id: 20130614-0229

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