If the first one has more RAM, it could potentially be operating at a higher speed of processing your automation. If the application being tested is operating at a (relatively) constant performance (such as a static amount of time between clicking a button and getting a response), it could be that the scripts are expecting the next button, form, component, page, window, etc, to be present before the application has actually presented it. We've had that occur in our environments.
If this is the case, solution would be to embed "Wait" routines in certain time critical sections of your automation where, after performing an action, you need to wait for something to process before you perform the next action.
Robert Martin [Hall of Fame] Please consider giving a Kudo if I write good stuff ----
Why automate? I do automated testing because there's only so much a human being can do and remain healthy. Sleep is a requirement. So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group. I love good food, good books, good friends, and good fun.
If Robert's advice does not help, send us your project along with the failed execution results. We will try to find out the cause of the test execution failure. You can send us the project via the Contact Support form (http://www.automatedqa.com/support/message/).
-- Dmitry Nikolaev
Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️