Windows 7 (VM, 2Gb RAM - this is what our production systems have)
Java 1.8.0_71 (AUT is Java desktop application, unfortunately I can't give access, and the nature of this issue prohibits a screen-share session)
When running a long-running test (we have a situation where we need to enter 1000s of orders in our POS system for logistics support testing), after approximately 1.5 hours Ranorex runs the JVM out of memory and crashes the JVM. This does not happen when Ranorex is not running (our POS is up for at least 10 hours every day on hundreds of systems in 90 stores and our test lab, someone would have noticed...).
I'm not sure that it's not a leak in my code, but I'm not doing anything outside of typical Ranorex usage here.
The exception in our AUT logs:
My guess is that this is part of the "new" Java instrumentation (which I still don't like...) and that there is a leak in it that is overrunning Java's memory pool.
Code: Select all
java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Unknown Source) at com.ranorex.SocketServer.run(SocketServer.java:58)
The system memory never gets above 60% load, which is one reason I don't think it's an issue with my test. If the test was the issue, the memory load on the system level would be rising continuously until maxed and I would probably lose control of the VM, which isn't happening.
In addition, I have tried restarting the AUT after a given number of iterations, but that doesn't seem to help, again leading me to believe this is a Ranorex issue since it is the only thing running on the system throughout.