← Back to team overview

sikuli-driver team mailing list archive

[Bug 1447096] Re: [1.1.0] OS X 10.10.3: IDE: running scripts acting on some Mac apps: work for about 60 seconds, then click/type get really slow --- workaround: use command line instead of app

 

@RaiMan

I've only been using SikuliX for a number months and so am still pretty
new with the tool as well as the Python language.


I'm currently using two versions of Mac OS, 10.12.6 and then I have a iMac on 10.13.2 which seems to be the problem child. Both Mac OS's are using Sikulix 1.1.2 and its the iMac that seems to be displaying the symptoms related this bug.

Automation Setup:-
iMac version 10.13.2
sikuliX version 1.1.2 (IDE)
Java version 8

macbook pro OS version 10.12.6
sikuliX version 1.1.2 (IDE)
Java version 8

Sikulix setup and test runs:-
I have no problems with the macbook pro, all tests run smoothly and quickly with no [debug] KeyPress: extended delay: 10010, just the iMac.

I have a single script with all my functions, then call upon them via
another script. As I mentioned before, I'm pretty new to Python and
coding in general.

The following messages are displayed when i run tests via the iMac:

[log] DOUBLE CLICK on L(2351,1246)@S(0)[0,0 2560x1440] (551 msec)

[log] DOUBLE CLICK on L(1646,396)@S(0)[0,0 2560x1440] (548 msec)

[log] DOUBLE CLICK on L(1813,362)@S(0)[0,0 2560x1440] (549 msec)
[log] TYPE "NewTest#TAB."

[log] TYPE "#ENTER."

[log] TYPE "#TAB."
[log] TYPE "A#TAB."

[log] TYPE "14#TAB."

[log] TYPE "MyStreet#TAB."

[log] TYPE "Wollongong#TAB."

[log] CLICK on L(2152,443)@S(0)[0,0 2560x1440] (525 msec)

[log] CLICK on L(1972,488)@S(0)[0,0 2560x1440] (524 msec)

[log] DOUBLE CLICK on L(1963,486)@S(0)[0,0 2560x1440] (549 msec)

[log] CLICK on L(2144,482)@S(0)[0,0 2560x1440] (525 msec)

[log] CLICK on L(2249,361)@S(0)[0,0 2560x1440] (524 msec)

[log] CLICK on L(2220,482)@S(0)[0,0 2560x1440] (524 msec)
[log] TYPE "2500#TAB."

[log] TYPE "0255733978#TAB."

[log] TYPE "junior.ese@xxxxxxxxxxxxxxxxxx#TAB."

[log] TYPE "mytestwebsite.com.au#TAB."

[log] TYPE "0452493687#TAB."

[log] TYPE "0255833978"

[debug] MouseDown: extended delay: 10010

[log] CLICK on L(1719,340)@S(0)[0,0 2560x1440] (10825 msec)

[debug] MouseDown: extended delay: 10010

[debug] MouseUp: extended delay: 10010
[log] DOUBLE CLICK on L(1646,578)@S(0)[0,0 2560x1440] (20755 msec)

[debug] MouseDown: extended delay: 10010

[debug] MouseUp: extended delay: 10010

[debug] MouseDown: extended delay: 10010

[debug] MouseUp: extended delay: 10010
[log] DOUBLE CLICK on L(1809,725)@S(0)[0,0 2560x1440] (40542 msec)
[log] TYPE "Billing Name Field"

[debug] KeyPress: extended delay: 10010

[debug] KeyPress: extended delay: 10010

[debug] KeyRelease: extended delay: 10010

[debug] KeyRelease: extended delay: 10011

[debug] KeyPress: extended delay: 10010

[debug] KeyRelease: extended delay: 10010

[debug] KeyPress: extended delay: 10010

[debug] KeyRelease: extended delay: 10010

[debug] KeyPress: extended delay: 10010

[debug] KeyRelease: extended delay: 10010

[debug] KeyPress: extended delay: 10010
[debug] KeyRelease: extended delay: 10010

[debug] KeyPress: extended delay: 10010

[debug] KeyRelease: extended delay: 10010

[debug] KeyPress: extended delay: 20009

[debug] KeyRelease: extended delay: 20009

[debug] KeyPress: extended delay: 20010

[debug] KeyRelease: extended delay: 20009

[debug] KeyPress: extended delay: 20010

[debug] KeyPress: extended delay: 20009

[debug] KeyRelease: extended delay: 20009

[debug] KeyRelease: extended delay: 20009

[debug] KeyPress: extended delay: 20009

[debug] KeyRelease: extended delay: 20009

[debug] KeyPress: extended delay: 20010

[debug] KeyRelease: extended delay: 20009

[debug] KeyPress: extended delay: 20010

[debug] KeyRelease: extended delay: 20010

[debug] KeyPress: extended delay: 20010

[debug] KeyRelease: extended delay: 20010

[debug] KeyPress: extended delay: 20010

[debug] KeyPress: extended delay: 20010

[debug] KeyRelease: extended delay: 20010

[debug] KeyRelease: extended delay: 12016


I had to cancel the test as it was hanging for a long time.  Let me know
if you have any ideas on where I could get this working correctly.  I'm
only using my macbook in the mean time as tests are working correctly.


Thanks for replying back to me btw.

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

Title:
  [1.1.0] OS X 10.10.3: IDE: running scripts acting on some Mac apps:
  work for about 60 seconds, then click/type get really slow ---
  workaround: use command line instead of app

Status in Sikuli:
  Fix Committed

Bug description:
  ************ workarounds:

  use this to start the IDE from a command line:
  java -jar /Applications/SikuliX.app/Contents/Java/sikulix.jar

  or use the IDE as usual, but do not run from inside the IDE, but in parallel from a Terminal session (command line)
  <path to your setup folder>/runsikulix -r yourScript.sikuli

  Since this seems to be some serious problem deep down in the Java
  Robot implementation with respect to OS X 10.10, a fix might take some
  time.

  The symptom: 
  about 60 seconds after the first Robot action, the robot extensively delays any mouse and keyboard actions and seems to do some features erroneously or even not at all.

  ------------------------------------------

  on OSX 10.10.3
  With nightly build 1.1.0 22-04-2015 and earlier versions

  i Get a error when i stop a simple loop script as it gets slow.

  for x in range(100):
  App.focus("dild")
  click(1)
  click(2)
  click(3)
  click(4)
  print("at " + str(x))

  i get to about 16 loops and its then get realy slow and finds the
  click´s every 10-20 sec...

  when i stop the script it promtes me that:
  Possible cause in case you did not touch the mouse while script was running:
  mouse actions are blocked generally or by formost application

  anybody have any ideas?

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


References