SikuliX freezes in the IDE, when using tools

Asked by Michael Blomli

Hi installed SikuliX today, and it worked fine the first minute or so. I made it take an screenshot and an click command, ran it and it worked fine. Then I clicked the take screenshot button again and it changes my icon to the cross for me to choose region, and it freezes there. Cant drag the region, and cant click anthing. I can alt + tab etc, but the system is still hanging on the screen capture. I have to force quit the program on ctrl alt del. Seems it works 50 % of the time for me with every tool in that program, it keeps hanging. I am getting an error in the console:

[info] IDE startup: 7,1 seconds

Exception in thread "AWT-EventQueue-0" java.awt.IllegalComponentStateException: component must be showing on the screen to determine its location
at java.awt.Component.getLocationOnScreen_NoTreeLock(Unknown Source)
at java.awt.Component.getLocationOnScreen(Unknown Source)
at javax.swing.text.JTextComponent$InputMethodRequestsHandler.getTextLocation(Unknown Source)
at sun.awt.im.InputMethodContext.getTextLocation(Unknown Source)
...

Thanks for any help.

Question information

Language:
English Edit question
Status:
Answered
For:
SikuliX Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
RaiMan (raimund-hocke) said :
#1

what SikuliX?
what System?
what Java?

Revision history for this message
Michael Blomli (mblom122) said :
#2

java version "1.8.0_162"
Java(TM) SE Runtime Environment (build 1.8.0_162-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.162-b12, mixed mode)
+++ trying to run SikuliX
+++ using: -Xms64M -Xmx512M -Dfile.encoding=UTF-8 -Dsikuli.FromCommandLine -jar C:\SikuliX\SikuliX 1.1.2-2\sikulix.jar

Also tried with SikuliX 1.1.1

I am using windows 10 Home - 64

Revision history for this message
RaiMan (raimund-hocke) said :
#3

I made some testing on my Windows 10 with the latest SikuliX 1.1.2.

I had one situation:
Exception in thread "AWT-EventQueue-0" java.awt.IllegalComponentStateException: component must be showing on the screen to determine its location

... but this did not freeze the IDE.
After that everything worked well.

Conclusion: you have to live with this quirk.
As long, as it does not lead to a constant "cannot use the IDE" situation, I cannot do anything, to track the problem down.

Can you help with this problem?

Provide an answer of your own, or ask Michael Blomli for more information if necessary.

To post a message you must log in.