We are sorry but we do not know how Ciege handled this problem.
Please answer the following questions:
Do you have a single process running all the time or several processes running the test? I.e. does that issue happen at the very beginning of the test/process lifetime or just anytime?
What kind of technology do you automate at the time the freeze occurs? Is there a DOM (Internet Explorer) open at the time or integrated in your application?
Another thing you could do when that freeze happens is opening Ranorex Spy and trying to search for the RanoreXPath the test process is performing the FindSingle on. Maybe Ranorex Spy freezes, too?
Where and whether the issue occurs is entirely random.
But it is always a search method which triggers Ranorex to freeze?
If you would know where it freezes you could hover, in debug mode, over the method and analyze the values of there parameters. Maybe there are some wrong values?
Callstack window (is that what you meant?)
Some kind of yes, the callstack shows you the stack data structure that stores information about the active subroutines of a computer program, -> stack trace: A stack trace (also called stack backtrace or stack traceback) is a report of the active stack frames at a certain point in time during the execution of a program, it represents the frames on the call stack at the time the current exception was thrown.
To get the specific "Callstack" at the specific time, just attach the running process (exe) to the debugger, and when it freezes, "pause" the execution and send us the Callstack. Please, make sure that the "Show External Methods" is enabled by right clicking in the Callstack pad.
Which Ranorex version are you using, the actual 3.2?
Ranorex Support Team