If you are familiar with sikuli scripting, you know there is a pair of functions built in called "observe()" and "onAppear()". The Observe function works by essentially starting a thread that continually scans for specific images in a given region of the screen. On the appearance of said image. a handler is called that handles the image (pop up) and ends that specific thread.
In my sikuli script I have about 30 of these observations running at one time (all on different region objects) This works fine most of the time, but I run into a problem when testing an application that uses java. I start to see weird bugs in the application that are only reproducible when I am running the observations. This leads me to believe that the 30 or so observations are slowing down the processor and thus causing issues in the application I am testing.
I am working to cut down the observations I need but even so I would still need at least 20 running during a given test. Is there any way I can allocate more resources for the observations, or is there any other solutions out there that I have not noticed?