sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

Public bug reported:

***************** workaround:

use Java 7

------------------------------------------
reported by: https://launchpad.net/~emaslov1

I have 4-hour sequence of about 50 Sikuli tests, driven by Python Unittest from command line, running well for last half of year.
Having got new Windows 7 64 bit machine, I copied there the whole Sikuli stuff, and then installed the last Java (8.31) from java.com . Now it's difficult to find old Java there...
Sikuli seemed to start working well, and IDE worked well with separate scripts, but, trying to run the whole sequence, Java crashed after five or six tests (40 min), with Windows crash message box, because of insufficient memory for it. Extending the memory limit in runsikulix.cmd had no effect at all.
The problem was finally solved with installation of older Java (7.67)
Java 8 seems to have some problems.

** Affects: sikuli
     Importance: High
     Assignee: RaiMan (raimund-hocke)
         Status: In Progress

** Changed in: sikuli
       Status: New => In Progress

** Changed in: sikuli
   Importance: Undecided => High

** Changed in: sikuli
     Assignee: (unassigned) => RaiMan (raimund-hocke)

** Changed in: sikuli
    Milestone: None => 1.1.0

** Description changed:

- Hello all,
- Not a question, I just hope it's useful info.
- Sikuli 1.1.0.
+ ***************** workaround:
+ 
+ use Java 7
+ 
+ ------------------------------------------
  I have 4-hour sequence of about 50 Sikuli tests, driven by Python Unittest from command line, running well for last half of year.
  Having got new Windows 7 64 bit machine, I copied there the whole Sikuli stuff, and then installed the last Java (8.31) from java.com . Now it's difficult to find old Java there...
  Sikuli seemed to start working well, and IDE worked well with separate scripts, but, trying to run the whole sequence, Java crashed after five or six tests (40 min), with Windows crash message box, because of insufficient memory for it. Extending the memory limit in runsikulix.cmd had no effect at all.
  The problem was finally solved with installation of older Java (7.67)
  Java 8 seems to have some problems.

** Description changed:

  ***************** workaround:
  
  use Java 7
  
  ------------------------------------------
+ reported by: https://launchpad.net/~emaslov1
+ 
  I have 4-hour sequence of about 50 Sikuli tests, driven by Python Unittest from command line, running well for last half of year.
  Having got new Windows 7 64 bit machine, I copied there the whole Sikuli stuff, and then installed the last Java (8.31) from java.com . Now it's difficult to find old Java there...
  Sikuli seemed to start working well, and IDE worked well with separate scripts, but, trying to run the whole sequence, Java crashed after five or six tests (40 min), with Windows crash message box, because of insufficient memory for it. Extending the memory limit in runsikulix.cmd had no effect at all.
  The problem was finally solved with installation of older Java (7.67)
  Java 8 seems to have some problems.

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

Title:
  [1.1.0] Windows 7 64: Java 8-31: crashes with insufficient memory
  after longer run (40 min here)

Status in Sikuli:
  In Progress

Bug description:
  ***************** workaround:

  use Java 7

  ------------------------------------------
  reported by: https://launchpad.net/~emaslov1

  I have 4-hour sequence of about 50 Sikuli tests, driven by Python Unittest from command line, running well for last half of year.
  Having got new Windows 7 64 bit machine, I copied there the whole Sikuli stuff, and then installed the last Java (8.31) from java.com . Now it's difficult to find old Java there...
  Sikuli seemed to start working well, and IDE worked well with separate scripts, but, trying to run the whole sequence, Java crashed after five or six tests (40 min), with Windows crash message box, because of insufficient memory for it. Extending the memory limit in runsikulix.cmd had no effect at all.
  The problem was finally solved with installation of older Java (7.67)
  Java 8 seems to have some problems.

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